Jupiter MCP has 2 tools with schemas visible in source code. Tool definitions are explicit in index.js using zod schemas. However, critical quality issues limit the score: (1) get-ultra-order has vague description lacking context on when/why to use it vs alternatives; (2) execute-ultra-order description lacks irreversible operation warning despite modifying blockchain state; (3) parameter descriptions are present but minimal (under 50 chars); (4) no output schema documentation, responses are JSON strings, not structured objects; (5) error handling returns raw error messages without recovery guidance; (6) no pagination, limits, or result structure definition; (7) execute-ultra-order references parameters (inputMint, outputMint, amount) in handler that don't exist in the input schema, indicating incomplete/inconsistent definition. Both tools exist in source with explicit registration via server.tool(), so no inference penalty applies.

• Add destructive operation warning to execute-ultra-order description: 'WARNING: This tool executes an irreversible blockchain transaction. Verify amounts and recipient before calling. Failed transactions may result in lost funds.'
• Document output schemas for both tools. Define expected response structure with field types and descriptions. Example: get-ultra-order returns {requestId: string, transaction: string, inAmount: bigint, outAmount: bigint, price: number}.
• Enhance error handling: catch API errors, categorize (retryable vs user-fixable), and return actionable guidance. E.g., 'Invalid mint address: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v not found on Solana mainnet. Verify address or search_solana_tokens() for alternatives.'
• Fix execute-ultra-order handler: remove references to inputMint, outputMint, amount parameters that don't exist in the schema. If needed, add them to the schema definition with descriptions.
• Expand parameter descriptions to 50 - 150 chars including format, constraints, and examples. E.g., 'inputMint: Solana token mint address (base58 format, 44 chars, e.g. EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v for USDC). Call get_solana_token_mints() to discover valid addresses.'
• Add rate limiting and timeout configuration. Tools call external APIs, set explicit timeouts (e.g., 30s for fetch) and document retry strategy to prevent agent hangs.
• Consider parameterizing the wallet/payer address instead of hard-coding it at startup. This allows multi-user scenarios and matches the chat data model (users operate with their own identities). Document whether the server is single-user or multi-user.