MCP server to integrate Jupiter Exchange with Cursor IDE for token swaps, price quotes, profit/loss calculation, and CSV export on Solana
Server has 4 tools with significant definition gaps. Tool descriptions are minimal (6-18 chars), far below the 50-200 char baseline for LLM-optimized descriptions. Schemas are present but descriptions lack context on WHEN to use each tool, WHAT it returns, and prerequisites. get_price and swap_tokens have identical parameter sets but no description distinguishing them. calculate_profit_loss and export_swaps have empty input schemas ({}), making their purpose unclear. No error recovery guidance, no output schema documentation, and no parameter constraints (e.g., token addresses should validate as Solana mint format). Tool names are verb-noun compliant but descriptions fail to explain irreversible consequences of swap_tokens.
Calculate P/L
Export swap history
Tool: get_price
Swap tokens using Jupiter
Tool descriptions critically short (6-20 chars). 'Tool: get_price', 'Calculate P/L', 'Export swap history' lack context on WHEN to use, WHAT is returned, and prerequisites. LLMs cannot determine tool selection intent from these descriptions.
calculate_profit_loss and export_swaps have empty input schemas ({}). No parameters are documented, making it impossible for LLMs to understand what these tools require or accept.
swap_tokens description ('Swap tokens using Jupiter') does not warn that this is an IRREVERSIBLE operation. Agents need explicit state-modification warnings to understand retry safety and consequences. Missing confirmation/dry-run pattern.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | <=2025-11-25 | v2 |
No output schema documentation. Handlers return JSON.stringify(response.data) or plain text, but LLMs cannot plan downstream calls without knowing field names, types, and structure. Missing documented return types.
Parameter descriptions missing for all tools. 'inputToken', 'outputToken', 'amount', 'slippageBps' have minimal descriptions (e.g., 'Input token mint address'). No format constraints, no examples of valid Solana mint addresses, no guidance on slippageBps range or defaults.