Skip to main content
Glama
AutomoxCommunity

Automox MCP Server

List Zones

list_zones
Read-onlyIdempotent

Retrieve a list of zones (organizations) in your Automox account. Use this to organize and manage devices by zone.

Instructions

List the zones (organizations) in the Automox account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
limitNo
output_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's statement that it lists zones adds minimal behavioral context beyond the schema. No additional details about pagination, rate limits, or side effects are provided.

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, concise sentence that front-loads the verb and resource. Every word is necessary and no extraneous content.

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 simplicity (list operation with optional pagination params) and the presence of an output schema, the description covers the core functionality. However, it could be improved by hinting at the optional parameters or the default behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning the parameters (page, limit, output_format) are undocumented in the schema and the description does not mention them at all. The description should compensate for the lack of schema descriptions but fails to do so.

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 provides a clear verb ('List'), resource ('zones'), and context ('in the Automox account'). It distinguishes the tool from siblings like 'list_zones_for_user' and 'get_zone'.

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 'list_zones_for_user' or 'get_zone'. The description does not specify any prerequisites or contextual triggers.

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/AutomoxCommunity/automox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server