Fix args required/optional annotations for contract tools#40
Fix args required/optional annotations for contract tools#40mefai-dev wants to merge 1 commit intobnb-chain:mainfrom
Conversation
Pull Request ReviewThis PR updates documentation for the EVM contract tools reference, specifically clarifying required vs optional Sensitive ContentNo sensitive content detected. Security IssuesNo serious security issues detected. Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits. |
## Summary - read_contract and write_contract both showed "args" without indicating required vs optional - In the MCP source, read_contract args are optional but write_contract args are required ## Type of Change - [x] Documentation fix ## Changes Made - read_contract: args → "args (optional array)" - write_contract: args → "args (required array)" - Improved ABI description: "Pass the contract ABI (full or relevant function entries)" ## Testing - [x] Verified against MCP source zod schemas
mefai-dev
force-pushed
the
fix/contract-args-annotation
branch
from
3421a26 to
e99f057
Compare
Pull Request ReviewThis PR updates documentation for EVM contract tools in Sensitive ContentNo sensitive content detected. Security IssuesNo serious security issues detected. Generated by Hashdit Bot. This tool can absolutely NOT replace manual audits. |
1 participant
Summary
read_contractargs marked as required when they're optionalwrite_contractargs not explicitly marked as requiredType of Change
Changes Made