Skip to main content
Glama

get-organization-appliance-vpn-statuses

Retrieve VPN status for all networks in a Meraki organization, including device status, peers, and uplinks.

Instructions

Show VPN status for networks in an organization. (read-only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
perPageNoThe number of entries per page returned. Acceptable range is 3 - 300. Default is 300.
startingAfterNoA token used by the server to indicate the start of the page. Often this is a timestamp or an ID but it is not limited to those. This parame
endingBeforeNoA token used by the server to indicate the end of the page. Often this is a timestamp or an ID but it is not limited to those. This paramete
networkIdsNoA list of Meraki network IDs to filter results to contain only specified networks. E.g.: networkIds[]=N_12345678&networkIds[]=L_3456
fieldsNoReturn only these top-level fields; omit for all. Available: deviceSerial, deviceStatus, exportedSubnets, merakiVpnPeers, networkId, networkName, thirdPartyVpnPeers, uplinks, vpnMode.
Behavior3/5

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

The description adds '(read-only)' which is a behavioral trait beyond the schema. However, with no annotations, the description carries the burden and omits other behaviors like pagination or rate limits. The addition is minimal but not misleading.

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 sentence plus a parenthetical note, with no wasted words. It is front-loaded and efficient.

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 tool has 6 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, pagination, or filtering behavior, leaving a significant gap in understanding.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description does not add any extra meaning to parameters beyond what the schema provides; it only repeats the purpose.

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 clearly states it shows VPN status for networks in an organization, which matches the tool name. It is specific enough to distinguish from siblings like 'get-organization-appliance-uplink-statuses' but does not explicitly differentiate from them in text.

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 on when to use this tool versus alternative siblings such as 'get-organization-appliance-uplink-statuses' or 'appliance-list-sitetositevpn'. A user or agent has no context for selection.

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/Flagler-County-BoCC/mcp-meraki'

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