Skip to main content
Glama

get-organization-appliance-uplink-statuses

Retrieve uplink status for all Meraki MX and Z series appliances in an organization, with optional filters by network, serial, or ICCID.

Instructions

List the uplink status of every Meraki MX and Z series appliances in the organization. (read-only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
perPageNoThe number of entries per page returned. Acceptable range is 3 - 1000. Default is 1000.
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 network IDs. The returned devices will be filtered to only include these networks.
serialsNoA list of serial numbers. The returned devices will be filtered to only include these serials.
iccidsNoA list of ICCIDs. The returned devices will be filtered to only include these ICCIDs.
fieldsNoReturn only these top-level fields; omit for all. Available: highAvailability, lastReportedAt, model, networkId, serial, uplinks.
Behavior2/5

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

The description notes the tool is 'read-only', but with no annotations, it fails to disclose behavioral traits like pagination behavior, rate limits, or data freshness. The schema includes pagination parameters, but the description does not explain how they work.

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 wasted words. It efficiently communicates the tool's purpose.

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 8 parameters and no output schema, the description is too minimal. It does not explain the return format, pagination details, or what 'uplink status' includes. Users would need to rely entirely on schema descriptions, which is insufficient for a complex tool.

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%, and the schema descriptions for each parameter are already clear. The tool description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 clearly states the verb 'List' and the resource 'uplink status of every Meraki MX and Z series appliances in the organization', specifying the exact scope and device types. This distinguishes it from siblings like 'get-organization-uplinks-statuses' which likely covers all uplinks.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'get-organization-uplinks-statuses' or 'get-organization-devices-statuses'. No contextual hints about prerequisites or excluded scenarios.

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