MCP server for Monad testnet interactions
Both tools have minimal descriptions (under 50 chars) and lack structured output schemas. Input schemas are present but sparse, only 'address' and 'amount' with basic string types, no enums, ranges, or validation hints. No error handling guidance, no parameter constraints, and no documentation of return types. The swap tool performs a WRITE operation but lacks confirmation/dry-run patterns. Tool names follow verb_noun convention (get-, swap-) but descriptions are too terse to guide LLM selection. No security considerations documented despite handling blockchain addresses and amounts.
Get MON balance for a given address
Swap MON to USDC for a given address and amount
No output schema documented. LLMs cannot plan downstream calls or extract structured data. get-mon-balance returns a formatted string; swap-mon-usdc returns a confirmation string. Neither declares field types or structure.
Descriptions are under 20 characters and provide no context for LLM selection. 'Get MON balance for a given address' and 'Swap MON to USDC for a given address and amount' lack WHEN to use, prerequisites, or side effects.
swap-mon-usdc is a destructive WRITE operation with no confirmation, dry-run, or idempotency guarantee. Agents could accidentally execute swaps without user approval.
Parameter 'address' lacks validation hints. No format constraint (must be 0x-prefixed hex), no length bounds, no error guidance if invalid. LLMs may pass malformed addresses.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 33 | 2026-07-28+ | v2 |
No error handling guidance. If address is invalid or swap fails, the server returns generic error strings. LLMs cannot determine if the error is retryable, user-fixable, or fatal.