VibeTrader MCP has a solid foundation with 9 tools that are mostly well-named and descriptive. All tools have descriptions (194-char baseline met), and all input parameters have type definitions and descriptions. However, there are critical gaps: (1) No output schemas are documented anywhere in the code, tools return JSON but what fields? what structure? (2) No error handling guidance, tools raise bare Exceptions without recovery hints (3) No parameter constraints (enums) despite tools like list_bots accepting a 'mode' parameter that should be constrained to 'paper'|'live'|None (4) Destructive tools (delete_bot) lack confirmation patterns or dry-run support (5) Tool composition could be improved, get_quote stands alone with no clear integration to bot creation/management. Tool naming is strong (all verb_noun), descriptions are adequate (10 - 200 chars each), but lack actionable guidance for LLM decision-making. Per-request auth via Bearer header is well-architected for multi-tenant safety, but this is not visible in tool definitions themselves.

• Add JSON Schema output definitions for every tool. Document bot object structure (id, name, status, mode, created_at, etc.), portfolio structure (positions array, balance, buying_power), quote structure (symbol, price, bid, ask, lastTrade). Include field types and which fields enable downstream tool calls (e.g. bot_id for start_bot).
• Convert mode parameter in list_bots and get_portfolio to enums: mode: {type: 'string', enum: ['paper', 'live']} instead of free-form string.
• Add recovery guidance to error responses. Replace 'Not authenticated!' with 'Not authenticated. Call authenticate(api_key) first, or provide Authorization: Bearer vt_... header.' Replace bare API errors with 'Bot not found. Call list_bots() to see available bots.'
• Implement confirmation for delete_bot. Either add a dry_run: bool parameter that returns success/failure without actually deleting, or add a confirm_delete_bot(bot_id, confirmation_code) two-step that issues a code first.
• Add pagination to list_bots if it can return many bots. Include limit: int (default 20, max 100) and offset: int parameters. Return {bots: [...], total: N, offset: M} so agent knows if there are more results.
• Enhance descriptions with dependency hints. E.g. 'Get current portfolio. Call this to check available capital before creating a new bot.' For get_quote: 'Get current stock price. Use this to understand market conditions before creating price-based trading bots.'
• Add idempotentHint/readOnlyHint/destructiveHint tool annotations (MCP 2026-07-28 feature). Mark list_bots, get_bot, get_portfolio, get_quote, authenticate with readOnlyHint: true. Mark delete_bot with destructiveHint: true.

Inferred effective spec: 2026-07-28+.

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