Crypto Portfolio MCP Server has 15 READ_ONLY tools with generally consistent schemas and descriptions. Naming is verb-forward and clear (get_*, check_*). Descriptions are present and substantive (80-200 chars typical), but lack actionable context for when/why to use each tool. Schemas are properly typed with enums where appropriate (e.g., timeframe, condition). However, no output schemas are documented, LLMs cannot plan downstream chaining without knowing what fields each tool returns. All tools are read-only, so no irreversible operation warnings are needed, but error handling guidance is absent. Security is sound (no API keys exposed as parameters), but composition could be stronger, some tools overlap (e.g., check_price_alert vs check_multiple_alerts). No tool annotations (readOnlyHint) are present.

• Document output schemas for all 15 tools. Example: get_total_portfolio_value should return {type: 'object', properties: {total_usd: {type: 'number'}, timestamp: {type: 'string'}, currency: {type: 'string'}}, required: ['total_usd']}. This enables LLM composition and reduces context window waste from unstructured output.
• Add error recovery guidance to tool descriptions. E.g., calculate_portfolio_pnl: 'Calculate total profit/loss for the portfolio. May return partial results if an exchange API is unavailable. If the call fails, check exchange status at status.binance.com or status.coinbase.com.'
• Consolidate check_price_alert and check_multiple_alerts into a single check_price_alerts tool accepting an array of alert objects. Single tool reduces LLM decision complexity and follows the batch-variants pattern.
• Expand parameter descriptions with ranges and constraints. E.g., get_biggest_movers.limit: 'Number of results per category (must be 1-50, default: 5)' and check_arbitrage_opportunities.min_profit_percentage: 'Minimum profit percentage threshold (must be 0.0-100.0, default: 1.0)'.
• Add readOnlyHint annotations to all tools. Register tools via app.tool() with an inputSchema and a 'readonly' flag (or via io.modelcontextprotocol/toolAnnotations extension). This signals to clients that all operations are safe to inspect.
• Include chaining IDs in responses where applicable. E.g., if get_current_prices returns coin metadata, also include a coin_id field for use in downstream analysis tools. This prevents forced lookup calls and reduces latency.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry