Skip to main content
Glama

get-organization-inventory-devices

Retrieve a filtered list of devices from an organization's inventory, with support for pagination and filters by status, serial, model, network, and tags.

Instructions

Return the device inventory for an 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
usedStateNoFilter results by used or unused inventory. Accepted values are 'used' or 'unused'.
searchNoSearch for devices in inventory based on serial number, mac address, or model.
macsNoSearch for devices in inventory based on mac addresses.
networkIdsNoSearch for devices in inventory based on network ids. Use explicit 'null' value to get available devices only.
serialsNoSearch for devices in inventory based on serials.
modelsNoSearch for devices in inventory based on model.
orderNumbersNoSearch for devices in inventory based on order numbers.
tagsNoFilter devices by tags. The filtering is case-sensitive. If tags are included, 'tagsFilterType' should also be included (see below).
tagsFilterTypeNoTo use with 'tags' parameter, to filter devices which contain ANY or ALL given tags. Accepted values are 'withAnyTags' or 'withAllTags', def
productTypesNoFilter devices by product type. Accepted values are appliance, camera, campusGateway, cellularGateway, secureConnect, sensor, switch, system
eoxStatusesNoFilter devices by EoX status. Accepted values are 'endOfSale', 'endOfSupport', 'nearEndOfSupport', or 'null'. Use 'null' to filter for devic
fieldsNoReturn only these top-level fields; omit for all. Available: claimedAt, countryCode, details, eox, licenseExpirationDate, mac, model, name, networkId, orderNumber, productType, serial, sku, tags.
Behavior2/5

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

Only notes 'read-only' which implies safe read operation, but with no annotations, the description should provide more behavioral context like pagination behavior, rate limits, or return format. It fails to disclose that the tool returns a list of devices with potential pagination tokens.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence plus parenthetical). While it avoids verbosity, it borders on underspecification. A single sentence is efficient but could be expanded slightly for clarity without losing conciseness.

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?

Despite complete schema parameter descriptions, the tool has 16 parameters and no output schema. The description fails to explain the overall behavior (e.g., pagination, filtering benefits, return structure), leaving the agent with insufficient context for effective use.

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 schema already documents all parameters thoroughly. The tool description adds no extra parameter meaning, earning the baseline score of 3.

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 the tool returns device inventory for an organization, and includes '(read-only)' to indicate no side effects. However, it does not differentiate from sibling tools like 'get-organization-devices' or 'get-organization-devices-statuses', missing nuanced distinction.

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, such as when to use inventory vs. status tools. No mention of prerequisites, pagination, or filtering strategies, leaving the agent without context for appropriate invocation.

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