Skip to main content
Glama

get-organization-devices

Retrieve a list of all devices assigned to networks in an organization. Filter by network, product type, tags, name, MAC, serial, model, and more.

Instructions

List the devices in an organization that have been assigned to a network. (read-only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
perPageNoThe number of entries per page returned. Acceptable range is 3 - 5000. 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
configurationUpdatedAfterNoFilter results by whether or not the device's configuration has been updated after the given timestamp
networkIdsNoOptional parameter to filter devices by network.
productTypesNoOptional parameter to filter devices by product type. Valid types are wireless, appliance, switch, systemsManager, camera, cellularGateway,
tagsNoOptional parameter to filter devices by tags.
tagsFilterTypeNoOptional parameter of value 'withAnyTags' or 'withAllTags' to indicate whether to return networks which contain ANY or ALL of the included t
nameNoOptional parameter to filter devices by name. All returned devices will have a name that contains the search term or is an exact match.
macNoOptional parameter to filter devices by MAC address. All returned devices will have a MAC address that contains the search term or is an exa
serialNoOptional parameter to filter devices by serial number. All returned devices will have a serial number that contains the search term or is an
modelNoOptional parameter to filter devices by model. All returned devices will have a model that contains the search term or is an exact match.
macsNoOptional parameter to filter devices by one or more MAC addresses. All returned devices will have a MAC address that is an exact match.
serialsNoOptional parameter to filter devices by one or more serial numbers. All returned devices will have a serial number that is an exact match.
sensorMetricsNoOptional parameter to filter devices by the metrics that they provide. Only applies to sensor devices.
sensorAlertProfileIdsNoOptional parameter to filter devices by the alert profiles that are bound to them. Only applies to sensor devices.
modelsNoOptional parameter to filter devices by one or more models. All returned devices will have a model that is an exact match.
fieldsNoReturn only these top-level fields; omit for all. Available: address, details, firmware, imei, lanIp, lat, lng, mac, model, name, networkId, notes, productType, serial, tags.
Behavior2/5

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

With no annotations, the description only notes read-only behavior. It does not disclose pagination, filtering impact, or return format. Schema provides parameter details, but behavioral context is lacking.

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 very short and front-loaded, efficiently conveying the core function. However, given tool complexity, it could be slightly expanded without sacrificing 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?

For a tool with 19 parameters, many siblings, and no output schema, the description is too minimal. It omits standard information like pagination behavior, filtering scope, and return values.

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 the baseline is 3. The description adds no extra meaning beyond the schema. Parameters are well-documented in schema.

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 lists devices assigned to a network, using a specific verb and resource. It hints at differentiation from siblings like 'get-organization-devices-statuses' but does not explicitly distinguish.

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 siblings, no prerequisites or exclusions mentioned. The '(read-only)' note is minimally helpful.

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