Skip to main content
Glama

getNetworkEvents

Retrieve events from a Meraki network by network ID. Filter by product type and set page size to control results.

Instructions

Get network events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkIdYes
productTypeNo
perPageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Async handler for getNetworkEvents tool, wraps the Meraki SDK's networks.getNetworkEvents method via call_meraki_method helper.
    async def getNetworkEvents(networkId: str, productType: str = None, perPage: int = 100) -> str:
        """Get network events"""
        params = {"networkId": networkId, "perPage": perPage}
        if productType:
            params['productType'] = productType
        return await call_meraki_method("networks", "getNetworkEvents", **params)
  • Sync handler for get_network_events tool, directly calls Meraki SDK's getNetworkEvents on the dashboard.networks object.
    @mcp.tool()
    def get_network_events(network_id: str, timespan: int = 86400, per_page: int = 100) -> str:
        """Get network events history"""
        events = dashboard.networks.getNetworkEvents(network_id, timespan=timespan, perPage=per_page)
        return json.dumps(events, indent=2)
  • meraki-mcp.py:655-657 (registration)
    Registration of get_network_events as an MCP tool using @mcp.tool() decorator.
    # Get network events
    @mcp.tool()
    def get_network_events(network_id: str, timespan: int = 86400, per_page: int = 100) -> str:
  • Registration of getNetworkEvents as an MCP tool using @mcp.tool() decorator.
    @mcp.tool()
    async def getNetworkEvents(networkId: str, productType: str = None, perPage: int = 100) -> str:
  • List of pre-registered tools including getNetworkEvents for the MCP configuration.
    "getNetworkEvents", "getNetworkDevices", "getDevice",
Behavior2/5

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

With no annotations, the description must convey behavioral traits. It only states 'Get network events' without disclosing whether it is read-only, any rate limits, pagination behavior (despite a perPage parameter), or the nature of the events.

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 very short (3 words) but under-specified; it is not meaningfully concise. The structure is minimal and does not front-load key information.

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

Completeness1/5

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

Given the tool has 3 parameters and an output schema, the description is drastically incomplete. It does not explain what events are returned, how to filter (productType), or pagination implications.

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 description does not explain the parameters networkId, productType, or perPage. Since the input schema has 0% description coverage, the description fully fails to add meaning beyond the property types.

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

Purpose3/5

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

The description 'Get network events' includes a verb ('Get') and a resource ('network events'), indicating the tool retrieves events. However, it does not differentiate from sibling tools like getNetwork or getNetworkClients; it lacks specifics on the type of events.

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. There is no mention of prerequisites, context, or scenarios where other tools might be preferred.

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