Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler

zdx_list_devices

Read-only

Retrieve a list of ZDX devices with filters for emails, user IDs, MAC addresses, and more. Supports JMESPath queries for custom client-side filtering.

Instructions

List ZDX devices with optional filtering (read-only) Supports JMESPath client-side filtering via the query parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailsNoFilter by email addresses.
user_idsNoFilter by user IDs.
mac_addressNoFilter by MAC address.
private_ipv4NoFilter by private IPv4 address.
location_idNoFilter by location ID(s).
department_idNoFilter by department ID(s).
geo_idNoFilter by geolocation ID(s).
sinceNoNumber of hours to look back (default 2h).
offsetNoOffset string for pagination (next_offset).
queryNoJMESPath expression for client-side filtering/projection of results.
serviceNoThe service to use.zdx

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The annotation readOnlyHint=true is confirmed by the description stating 'read-only'. The description adds information about JMESPath client-side filtering via the query parameter. However, it does not disclose pagination behavior (offset parameter), rate limits, or other operational traits that would be valuable beyond the annotation.

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 extremely concise at two sentences and 18 words, front-loaded with the primary action and resource. Every sentence adds value, with no fluff or redundancy.

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 having 11 parameters (many for filtering), pagination support, and an output schema, the description is minimal. It does not explain the purpose of various filters, the pagination mechanism, or how the output is structured. This is insufficient for the tool's complexity.

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?

With 100% schema description coverage, the baseline is 3. The description mentions only the 'query' parameter, but its purpose is already in the schema. No additional parameter semantics are provided beyond the schema descriptions.

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 action ('List') and resource ('ZDX devices'). It specifies optional filtering and read-only nature. While it distinguishes the tool as ZDX-specific, it does not explicitly differentiate from sibling tools like zia_list_devices or zcc_list_devices, but the purpose is unambiguous.

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 offers no guidance on when to use this tool versus alternatives. Among many sibling tools, there is no mention of when to prefer this over other device listing tools (e.g., zia_list_devices, zcc_list_devices) or what context is appropriate.

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/zscaler/zscaler-mcp-server'

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