Apollo MCP Server provides 4 tools for GraphQL introspection and execution. Tool naming follows the action-verb pattern (introspect, search, validate, execute) which is good. However, critical gaps exist: (1) Tool descriptions are present but generic and lack actionable context about when to use each tool vs alternatives; (2) No visible input/output schemas in the provided source code, cannot verify parameter types, constraints, or response structures; (3) No evidence of parameter descriptions or constraints; (4) The 'execute' tool is destructive (WRITE risk) but descriptions do not explicitly state mutation consequences or require confirmation patterns; (5) Error handling strategy is not visible in the provided source.

• Add explicit JSON Schema definitions for each tool's input and output. For 'introspect', document whether 'schema' is a URL, string, or file path, and what fields are returned (types, fields, arguments, etc.). For 'search', specify the query format (regex, substring, fuzzy?) and response structure (matching_types[], matching_fields[], etc.). For 'execute', document GraphQL operation format (query string, variables object, operationName).
• Expand tool descriptions to 100 - 200 characters following LLM-optimization guidance: state WHAT the tool does, WHEN to use it, and any prerequisites. Example for 'introspect': 'Retrieve the complete GraphQL schema definition including all types, fields, arguments, and directives. Call this first to understand the API structure before searching or validating operations.' Current descriptions are ~40-60 chars and lack context.
• Add parameter descriptions with type, format, constraints, and examples. For 'search', document: 'query (string, required): Search pattern for types and fields. Supports substring and regex matching. Example: "User" or "@.*Cache". Results limited to 50 matches.' For 'execute', document: 'operation (string, required): GraphQL query/mutation string with variables. Format: standard GraphQL operation syntax. Variables must be passed as separate parameter if needed.'
• For 'execute' tool, explicitly state in description: 'WARNING: Executes mutations and queries against the configured GraphQL endpoint. This tool can modify data. Use validate() first to check syntax.' Consider adding an optional 'dry_run' or 'confirm' parameter for destructive operations, or implement a separate 'execute_read_only' tool for queries.

Inferred effective spec: 2025-06-18+.

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