Critical failure across all dimensions. No tool definitions are visible in the provided source code. The smoke.py file only lists expected tool names as strings in a set; it does not show actual tool registration, schemas, descriptions, or parameter definitions. Per the hard scoring rule: 'If you cannot see the actual tool definition in the source (only inferred): cap that tool's overall at 50.' Since ALL 11 tools are inferred only from the EXPECTED_TOOLS set, and no schema/description data is provided, the entire server cannot be evaluated. The mcp.json shows only a remote endpoint URL and auth header, no tool metadata. Without access to the actual MCP server implementation (the backend at https://envelopebudget.com/mcp), we cannot verify schemas, descriptions, parameter types, or error handling. This is a remote HTTP service with no source code provided.

• Provide complete tool definitions in the source repository. Include tool name, description (50 - 200 chars), input schema with typed parameters, and output schema. Currently only a smoke test client is visible.
• Add parameter descriptions for all inputs. Even if a tool accepts no parameters today, document why (e.g., 'This tool requires no parameters; it returns all budgets for the authenticated user.').
• Document output schemas with field types and descriptions. E.g., list_budgets should specify: returns {budgets: [{id: string, name: string, balance: number, ...}], total_count: number}.
• Implement error handling with recovery guidance. E.g., 'User not found. Try search_users() with a partial name.' or 'Rate limit exceeded. Retry after 60 seconds.'
• Add pagination support to list_* tools. Accept limit and offset/cursor parameters; return total_count or next_cursor. Baseline: list tools should cap results at 20 - 50 items.