Skip to main content
Glama

get-organization-devices-statuses

Retrieve the current status of all Meraki devices in your organization, with optional filters by network, serial, status, or product type. Monitor device health at a glance.

Instructions

List the status of every Meraki device 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
networkIdsNoOptional parameter to filter devices by network ids.
serialsNoOptional parameter to filter devices by serials.
statusesNoOptional parameter to filter devices by statuses. Valid statuses are ['online', 'alerting', 'offline', 'dormant'].
productTypesNoAn optional parameter to filter device statuses by product type. Valid types are wireless, appliance, switch, systemsManager, camera, cellul
modelsNoOptional parameter to filter devices by models.
tagsNoAn optional parameter to filter devices by tags. The filtering is case-sensitive. If tags are included, 'tagsFilterType' should also be incl
tagsFilterTypeNoAn optional parameter of value 'withAnyTags' or 'withAllTags' to indicate whether to return devices which contain ANY or ALL of the included
fieldsNoReturn only these top-level fields; omit for all. Available: components, gateway, ipType, lanIp, lastReportedAt, mac, model, name, networkId, primaryDns, productType, publicIp, secondaryDns, serial, status, tags.
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It declares the tool is 'read-only', indicating no side effects, but does not disclose pagination behavior, rate limits, or error handling. For a read operation, this is minimally adequate but could be more explicit.

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 with a parenthetical, making it very concise. Every word is informative—verb, resource, scope, and read-only hint. No fluff or unnecessary detail.

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

Completeness4/5

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

Given the tool's complexity (12 parameters, no output schema) and rich schema descriptions, the description is sufficient for a listing tool. It doesn't need to explain return values since no output schema exists, and the schema documents parameters well. Sibling tools exist but are more specific, so the description correctly implies this covers all device types.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema, and parameters like 'startingAfter' and 'endingBefore' are already well-documented. No improvement needed.

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 'status of every Meraki device', and the scope 'in the organization'. It distinguishes from siblings like 'get-organization-devices' which lists devices without status, and 'get-organization-devices-statuses-overview' which aggregates statuses. The explicit '(read-only)' also clarifies the operation type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide explicit guidance on when to use this tool versus alternatives like 'get-organization-devices-statuses-overview' or device-specific status tools. It implies usage for listing individual device statuses, but lacks when-not-to-use or context with siblings.

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