Single tool 'whoami' with empty input schema and minimal description. No parameter documentation, no output schema specification, no error handling guidance. The tool definition is visible in server.ts but lacks the rigor expected for production. Description is 95 chars (within acceptable range) but provides no context on when to use it, what it returns, or how to handle errors. Input schema is completely empty ({}), violating the requirement that every parameter be described. No tool annotations present.

• Add explicit input schema with type definitions. Even if 'whoami' takes no parameters, declare schema: {} with a description explaining why no inputs are needed.
• Document the output schema: specify that the response contains 'key_name' (string) and 'scopes' (array of strings), e.g., {"key_name": "sk-...", "scopes": ["read:items", "write:items"]}.
• Expand description to 150-200 chars: 'Validate the API key and retrieve its associated name and permission scopes. Call this first to confirm authentication and discover available operations.'
• Add error handling guidance: 'Returns 401 if the API key is invalid or expired. Returns 403 if the key lacks required scopes. Returns 5xx if the backend is unavailable.'
• Rename tool to 'check_api_key' or 'get_current_user' to follow verb_noun convention and improve LLM discoverability.

Inferred effective spec: 2026-07-28+.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained