Skip to main content
Glama

networks-list-clients

Retrieve a filtered list of clients that have used a specific network within a given timespan. Supports filtering by status, IP, MAC, OS, VLAN, and more.

Instructions

List the clients that have used this network in the timespan. (read-only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkIdYesNetwork ID
t0NoThe beginning of the timespan for the data. The maximum lookback period is 31 days from today.
timespanNoThe timespan for which the information will be fetched. If specifying timespan, do not specify parameter t0. The value must be in seconds an
perPageNoThe number of entries per page returned. Acceptable range is 3 - 5000. Default is 10.
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
statusesNoFilters clients based on status. Can be one of 'Online' or 'Offline'.
ipNoFilters clients based on a partial or full match for the ip address field.
ip6NoFilters clients based on a partial or full match for the ip6 address field.
ip6LocalNoFilters clients based on a partial or full match for the ip6Local address field.
macNoFilters clients based on a partial or full match for the mac address field.
osNoFilters clients based on a partial or full match for the os (operating system) field.
pskGroupNoFilters clients based on partial or full match for the iPSK name field.
descriptionNoFilters clients based on a partial or full match for the description field.
vlanNoFilters clients based on the full match for the VLAN field.
namedVlanNoFilters clients based on the partial or full match for the named VLAN field.
recentDeviceConnectionsNoFilters clients based on recent connection type. Can be one of 'Wired' or 'Wireless'.
fieldsNoReturn only these top-level fields; omit for all. Available: adaptivePolicyGroup, description, deviceTypePrediction, firstSeen, groupPolicy8021x, id, ip, ip6, ip6Local, lastSeen, mac, manufacturer, namedVlan, notes, os, pskGroup, recentDeviceConnection, recentDeviceMac, recentDeviceName, recentDeviceSerial, smInstalled, ssid, status, switchport, usage, user, vlan, wirelessCapabilities.
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only adds '(read-only)', which hints at safety but does not disclose other behaviors like pagination, rate limits, or data freshness.

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

Conciseness3/5

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

The description is very short (one sentence) and front-loaded with the purpose and read-only hint. However, it could be more structured or include additional essential details.

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?

Given the tool has 18 parameters, no output schema, and no annotations, the description is insufficient. It does not explain pagination, filtering use, or what data is returned, making it incomplete 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?

The input schema has 100% coverage with descriptions for all parameters. The description does not add extra meaning or examples beyond what the schema provides, so it meets the baseline.

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 verb 'list' and the resource 'clients', and specifies the scope 'that have used this network in the timespan'. However, it does not distinguish itself from the sibling tool 'networks-get-clients', which might have a similar purpose.

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?

The description provides no guidance on when to use this tool versus alternatives like 'networks-get-clients' or other list tools. There is no mention of prerequisites or exclusions.

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