MCP server for trading stocks via Zerodha Kite Connect API
Critical failures across all dimensions. All 4 tools lack descriptions entirely (0/4 have non-empty descriptions). Parameter descriptions are null for all inputs. No output schemas documented. Tool names use hyphens instead of verb_noun convention. No error handling, validation, or recovery guidance. The two financial tools (buy-a-stock, sell-a-stock) are IRREVERSIBLE operations with zero safety mechanisms, no confirmation patterns, and no audit trails. This server is not production-ready.
All 4 tools completely lack descriptions. LLMs cannot determine when or why to select these tools. This violates the foundational pattern:tool-description requirement.
All parameter descriptions are null. LLMs cannot infer what 'stock', 'qty', 'a', 'b' mean without explicit descriptions. This violates pattern:tool-description.
Irreversible financial operations (buy-a-stock, sell-a-stock) have zero safety mechanisms: no dry-run, no confirmation step, no audit trail, no error recovery guidance. Agents can execute real trades without safeguards.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 24 | 2026-07-28+ | v2 |
Tool names use kebab-case (add-two-number) instead of verb_noun convention (add_two_numbers). This violates naming baseline: 90% of A+ tools start with action verbs in snake_case.
No output schemas documented. LLMs cannot plan downstream calls or extract structured data. All tools return generic text responses without field definitions.