Canopii is a security scanner for MCP servers, not a functional MCP server itself. The two test fixtures ('lookup' and 'run') are minimal examples used for testing the scanner's detection logic. Both tools lack proper descriptions (under 20 chars), have minimal schemas, and are intentionally designed to demonstrate security issues (injection markers, destructive scope). The 'lookup' tool has a basic schema but trivial description. The 'run' tool has no schema visible and a description that doesn't explain parameters. Neither tool follows production naming conventions or includes parameter descriptions. These are test fixtures, not production tools.

• Expand 'lookup' description to 50-200 chars explaining what record type, what ID format, what fields are returned, and when to use it.
• Add full parameter descriptions to both tools. For 'lookup', explain the 'id' parameter (format, example, constraints). For 'run', document 'cmd' type, allowed commands, and security implications.
• Add explicit input schemas with type constraints. For 'run', add enum or pattern to restrict commands to a safe whitelist, not arbitrary shell execution.
• Document output schemas. What does 'lookup' return? What fields? What does 'run' return (stdout, stderr, exit code)?
• Add error handling guidance: 'If lookup fails with 404, try search_records() first.' For 'run', document timeout behavior and non-zero exit code handling.