Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler

zia_list_devices

Read-only

Retrieve a list of ZIA devices with optional filters such as name, user IDs, and pagination. Use client-side filtering via JMESPath expressions.

Instructions

List ZIA devices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
pageNo
queryNoOptional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Field names are exactly what the Zscaler API returns. Examples: "[?enabled==`true`]", "[*].{name: name, id: id}", "length(@)". Omit to get the full records.
user_idsNo
page_sizeNo
include_allNo
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the description's 'List' is consistent but adds no additional behavioral context. It does not mention pagination, rate limits, or other traits that would help the agent anticipate behavior beyond what annotations provide.

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

Conciseness2/5

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

The description is extremely concise at three words, but it is under-specified rather than efficient. It lacks structure and essential details, making it insufficient for an agent to understand usage without additional context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 6 parameters, no output schema, and a minimal description, the tool definition is very incomplete. The description provides no guidance on filtering, pagination, or what the response contains, leaving significant gaps for an AI agent.

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 only 17% (only the 'query' parameter has a description). The tool description adds no information about parameters, leaving 5 of 6 parameters undocumented. Given low schema coverage, the description must compensate but fails to do so.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'List ZIA devices', which clearly indicates the verb and resource. However, it does not differentiate from sibling tools like 'zia_list_devices_lite', which likely has a similar purpose. The agent may need more context to choose the correct tool.

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. Siblings such as 'zia_list_devices_lite' exist, but the description offers no differentiation or context about prerequisites, filters, or intended use cases.

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