Skip to main content
Glama

get_mcp_config

Retrieve the current MCP configuration to inspect server settings and parameters for the Meraki environment.

Instructions

Get MCP configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'get_mcp_config' tool handler function, decorated with @mcp.tool(). Returns a JSON string describing the MCP configuration including mode, pre-registered tools, generic API caller info, and runtime settings (read-only mode, caching, max tokens, etc.).
    @mcp.tool()
    async def get_mcp_config() -> str:
        """Get MCP configuration"""
        return json.dumps({
            "mode": "hybrid",
            "description": "12 pre-registered tools + call_meraki_api for full API access",
            "pre_registered_tools": ["getOrganizations", "getOrganizationAdmins", "getOrganizationNetworks",
                                      "getOrganizationDevices", "getNetwork", "getNetworkClients",
                                      "getNetworkEvents", "getNetworkDevices", "getDevice",
                                      "getNetworkWirelessSsids", "getDeviceSwitchPorts", "updateDeviceSwitchPort"],
            "generic_caller": "call_meraki_api - access all 804+ methods",
            "total_available_methods": "804+",
            "read_only_mode": READ_ONLY_MODE,
            "caching_enabled": ENABLE_CACHING,
            "cache_ttl_seconds": CACHE_TTL_SECONDS,
            "file_caching_enabled": ENABLE_FILE_CACHING,
            "max_response_tokens": MAX_RESPONSE_TOKENS,
            "max_per_page": MAX_PER_PAGE,
            "response_cache_dir": RESPONSE_CACHE_DIR,
            "organization_id_configured": bool(MERAKI_ORG_ID),
            "api_key_configured": bool(MERAKI_API_KEY)
        }, indent=2)
  • The tool is registered as an MCP tool via the @mcp.tool() decorator on line 649, where 'mcp' is a FastMCP instance created on line 30.
    @mcp.tool()
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must convey behavior. 'Get' implies a read-only operation, but no details are given about caching, cost, or whether the configuration changes. The simplicity of the tool (no params) limits risk, but more transparency would be beneficial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no unnecessary words. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (no parameters, read-only) and the presence of an output schema, the description is complete enough for an agent to understand the tool's purpose. It could be slightly more descriptive, but it suffices.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, and schema description coverage is 100%. The description does not need to add parameter-level detail, and it correctly implies that no inputs are required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get MCP configuration' clearly states the action (get) and the resource (MCP configuration). It distinguishes itself from sibling tools like getDevice or getNetwork, which target different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description does not mention context, prerequisites, or typical scenarios, leaving the agent without decision support.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CiscoDevNet/meraki-magic-mcp-community'

If you have feedback or need assistance with the MCP directory API, please join our Discord server