Skip to main content
Glama

wireless-list-bydevice

Retrieve wireless BSSID status information for each device in your organization. Filter by network, serial, or BSSID to focus on specific devices.

Instructions

List status information of all BSSIDs in your organization. (read-only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
networkIdsNoOptional parameter to filter the result set by the included set of network IDs
serialsNoA list of serial numbers. The returned devices will be filtered to only include these serials.
bssidsNoA list of BSSIDs. The returned devices will be filtered to only include these BSSIDs.
hideDisabledNoIf true, the returned devices will not include disabled SSIDs. (default: true)
perPageNoThe number of entries per page returned. Acceptable range is 3 - 500. Default is 100.
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
fieldsNoReturn only these top-level fields; omit for all. Available: items, meta.
Behavior4/5

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

Explicitly marks itself as read-only, which is a key behavioral trait. With no annotations, this is helpful. However, it does not disclose pagination or rate limits, though the schema parameters hint at pagination.

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?

One sentence plus a parenthetical note. Very concise, all necessary information is front-loaded. No filler.

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?

No output schema, so the description should explain what 'status information' contains. It does not. Also, the 'bydevice' grouping is not explained. For a tool with 9 parameters, the description is too minimal.

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 each parameter has a reasonable description. The main description adds no extra meaning beyond the schema. Baseline score of 3 is appropriate.

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?

Clearly states it lists status information of all BSSIDs in the organization. Verb and resource are specific. However, the name includes 'bydevice' suggesting grouping by device, which is not reflected in the description, and sibling 'wireless-list-status' could be confused.

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 'wireless-list-status'. No when-not-to-use or prerequisites mentioned.

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