Skip to main content
Glama

get-organization-uplinks-statuses

Retrieve uplink status for all Meraki MX, MG, and Z series devices in an organization, filtering by network, serial, or ICCID.

Instructions

List the uplink status of every Meraki MX, MG and Z series devices 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?

No annotations provided, so the description carries full burden. It only mentions '(read-only)', but lacks disclosure of pagination, filtering effects, or any side effects. Minimal behavioral insight beyond the read-only hint.

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, clear sentence with a parenthetical read-only hint. Every word is informative with no redundancy or wasted space.

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?

With 8 parameters, no output schema, and no explanation of what 'uplink status' entails or how results are returned, the description is insufficient for an agent to fully understand the tool's behavior and output without external knowledge.

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% with all parameters described in the schema. The description adds no extra semantic value beyond the schema, meeting the baseline expectation.

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', the resource 'uplink status', and specifies device series (MX, MG, Z series) and scope (organization). This differentiates it from siblings like 'get-organization-appliance-uplink-statuses' which likely covers only appliances.

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 alternatives like 'get-organization-appliance-uplink-statuses' or other listing tools. The description only states the action without context on usage scenarios or prerequisites.

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