The @dappql/mcp server has critical gaps in tool definitions. While 14 tools are listed, the provided source code does NOT include the actual tool registration code, schemas, or descriptions. Only package.json files are visible. Without access to the tool implementation in packages/mcp/src/tools/*.ts, I cannot verify schemas, parameter types, descriptions, or error handling. The server lists 14 tools across metadata.ts, chain.ts, and codegen.ts, but without the actual TypeScript source showing schemas, descriptions, and parameter definitions, the quality cannot be assessed.

• Provide the actual TypeScript source code from packages/mcp/src/tools/metadata.ts, packages/mcp/src/tools/chain.ts, and packages/mcp/src/tools/codegen.ts showing tool registration with Server.tool() calls or equivalent MCP SDK method.
• For EACH of the 14 tools, add a description (50-200 chars) answering: What does it do? When should the LLM call it instead of a similar tool? What does it return?
• For list_* tools (listContractsTool, listPluginsTool), add pagination parameters (limit, offset/cursor) and document whether results are paginated. If returning more than 50 items, cap the response and offer pagination.
• For all tools accepting parameters, make schemas explicit with proper JSON Schema including 'type', 'description', and 'required' for each parameter. Use enum constraints for known valid values (e.g., contract type, plugin category).
• For getContractTool and searchMethodsTool, document the output schema clearly. What fields does a contract or method object contain? Are there IDs that chain to callReadTool or callWriteTool?
• For simulateWriteTool and callWriteTool, add explicit error handling guidance in descriptions: 'On failure, return {error, reason, retryable}. If retryable, suggest simulateWriteTool first.'
• For callWriteTool, add confirmation or dry-run support. Consider a 'dryRun: true' parameter or a multi-step pattern: simulateWriteTool → user approval → callWriteTool.
• Rename tools to drop the 'Tool' suffix and use snake_case with action verbs: get_dappql_reference, get_project_info, get_chain_state, list_contracts, list_plugins, get_contract, search_methods, call_read, multicall, get_events, get_transaction, simulate_write, call_write, regenerate.