The Meraki Monitor MCP server has significant quality gaps across naming, descriptions, schemas, and error handling. While all 16 tools are explicitly defined with names following verb_noun patterns (get_*), the implementation suffers from critical issues: (1) Most tools accept no parameters or undocumented parameters (8 tools have empty input schemas with zero parameter descriptions). (2) Tool descriptions are present but generic and lack actionable context about when to use each tool vs. alternatives. (3) Output schemas are completely undocumented, responses are returned as raw JSON.dumps() with no type information. (4) Error handling is minimal: some tools check for missing env vars and return JSON error objects, but most lack recovery guidance. (5) All tools are read-only, mitigating some risk, but the lack of pagination, rate limiting, and output constraints means large API responses can blow context windows. (6) The server uses environment variables for configuration (MERAKI_API_KEY, MERAKI_ORG_ID, MERAKI_NETWORK_ID) which is correct for secret injection, but hard-codes many API calls to a single organization/network, limiting flexibility.

• Document output schemas for all 16 tools. Specify the structure of the JSON returned by each tool so LLMs know what fields to expect. E.g., 'Returns array of {id, name, status, createdAt, ...}' for get_organizations.
• Enhance descriptions for the 9 parameter-less tools (get_organizations, get_organization_details, etc.). Explain what data is returned, when to use each tool, and how it differs from similar tools. E.g., get_organization_details returns config and health; get_organization_status returns real-time health indicators only.
• Add pagination support to list tools. Add limit, offset, and page parameters with constraints (e.g., limit 1-100, default 20). Return total_count and next_offset in responses.
• Parameterize organization_id and network_id instead of hard-coding them from .env. Allow LLMs to query any organization/network the API key has access to. Fall back to .env defaults if not provided.
• Add comprehensive error handling with recovery guidance. Catch API errors (404 resource not found, 403 permission denied, 429 rate limited) and return structured error responses with actionable next steps. E.g., 'Channel not found. Call get_networks() first to see available networks.'
• Add constraints to numeric parameters. For timespan_days: min=1, max=365. For timespan (seconds): min=60, max=2592000 (30 days). For client_id and serial: describe expected format (hex string, MAC address, serial number format).
• Implement tool annotations using the MCP 2026-07-28 spec. Add readOnlyHint=true to all tools to signal they do not modify state.