MCP Server for Hackathon - Integrates Helius SDK to provide Solana blockchain asset queries
Single tool with well-structured schema and reasonable descriptions. Tool name follows verb_noun pattern (helius_getAssetsByOwner). Input schema is complete with Zod validation and all parameters described. However, output schema is not documented, response is raw JSON stringified without field documentation. Error handling returns basic error messages but lacks recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite READ_ONLY risk classification. Descriptions are adequate (194 chars for tool, 50-80 chars per param) but could be more LLM-optimized with explicit WHEN/WHY guidance.
Get a list of assets owned by an address. This is the fastest way to get all the NFTs and fungible tokens owned by a wallet on Solana.
Output schema not documented. Tool returns JSON.stringify(response) without specifying what fields the response contains (e.g., items[], total, next_cursor). LLMs cannot plan downstream operations or extract specific fields without knowing the structure.
No tool annotations despite READ_ONLY risk classification. Tool should declare readOnlyHint: true in metadata so agents know it is safe to call without side effects. This enables confident retry and caching strategies.
Error handling lacks recovery guidance. Catch block returns generic 'Error fetching assets: <message>' without suggesting next steps (e.g., 'Check that ownerAddress is a valid Solana wallet' or 'Verify HELIUS_API_KEY is set').
No pagination limit enforcement. Tool accepts limit parameter but does not cap it. Unbounded limit could cause LLM to request 10,000+ results, exhausting context window and API quota.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
displayOptions parameter is nested object but lacks clear enum constraints. showFungible defaults to false but description does not explain why or when to set true. Ambiguous parameter relationships.