Skip to main content
Glama
CiscoDevNet

Meraki Magic MCP

by CiscoDevNet
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

getNetworkWirelessSsids

Retrieve all wireless SSIDs configured on a Meraki network by providing the network ID.

Instructions

Get wireless SSIDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkIdYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • meraki-mcp-dynamic.py:479-482 (handler)
    The MCP tool 'getNetworkWirelessSsids' handler in meraki-mcp-dynamic.py - an async function decorated with @mcp.tool() that calls call_meraki_method('wireless', 'getNetworkWirelessSsids', networkId=networkId). This is the direct tool implementation.
    @mcp.tool()
async def getNetworkWirelessSsids(networkId: str) -> str:
    """Get wireless SSIDs"""
    return await call_meraki_method("wireless", "getNetworkWirelessSsids", networkId=networkId)
  • meraki-mcp-dynamic.py:479-482 (registration)
    Registration of 'getNetworkWirelessSsids' as an MCP tool via @mcp.tool() decorator in meraki-mcp-dynamic.py (pre-registered common tool).
    @mcp.tool()
async def getNetworkWirelessSsids(networkId: str) -> str:
    """Get wireless SSIDs"""
    return await call_meraki_method("wireless", "getNetworkWirelessSsids", networkId=networkId)
  • meraki-mcp-dynamic.py:655-658 (registration)
    List of pre-registered tools in get_mcp_config() listing 'getNetworkWirelessSsids' among the 12 pre-registered tools.
    "pre_registered_tools": ["getOrganizations", "getOrganizationAdmins", "getOrganizationNetworks",
                          "getOrganizationDevices", "getNetwork", "getNetworkClients",
                          "getNetworkEvents", "getNetworkDevices", "getDevice",
                          "getNetworkWirelessSsids", "getDeviceSwitchPorts", "updateDeviceSwitchPort"],
  • meraki-mcp.py:469-473 (handler)
    The get_wireless_ssids tool (with snake_case name) in meraki-mcp.py - calls async_get_wireless_ssids which wraps dashboard.wireless.getNetworkWirelessSsids via to_async(). This is the static (non-dynamic) implementation.
    @mcp.tool()
async def get_wireless_ssids(network_id: str) -> str:
    """Get wireless SSIDs for a network"""
    ssids = await async_get_wireless_ssids(network_id)
    return json.dumps(ssids, indent=2)
  • meraki-mcp.py:78-78 (helper)
    Async wrapper creation for dashboard.wireless.getNetworkWirelessSsids using the to_async() helper, bound to the variable async_get_wireless_ssids.
    async_get_wireless_ssids = to_async(dashboard.wireless.getNetworkWirelessSsids)

Tool Definition Quality

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It states only the action without disclosing side effects, authentication needs, or behavior for empty results. The tool appears read-only but lacks explicit safety cues.

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

Conciseness2/5

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

The description is too brief to be considered appropriately concise. It fails to provide necessary context, making it under-specified rather than succinct.

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

Completeness2/5

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

Given the availability of an output schema, the description could be minimal but still misses key details like what the tool returns (list vs. details), preconditions, and error states. It is insufficient for safe and correct invocation.

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

Parameters1/5

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

The input schema has 0% description coverage for the single parameter networkId, and the tool description adds no extra meaning. The parameter's role and source remain unexplained.

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

Purpose4/5

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

The description 'Get wireless SSIDs' clearly indicates retrieval of SSIDs. It is a specific verb+resource combination, though it does not differentiate from other get* siblings.

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 like getNetwork or getNetworkClients. The context of use is only implied by the tool name.

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