Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler

zpa_list_isolation_policy_rules

Read-only

Retrieve ZPA isolation policy rules to inspect and review access control configurations. Use query filters, pagination, and search options to locate specific policies for security audits.

Instructions

List ZPA isolation policy rules (read-only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
queryNoOptional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: "[?enabled==`true`]", "[*].{name: name, id: id}", "length(@)". Omit to get the full records. IMPORTANT: field names are the keys of the returned records, which are usually snake_case (`custom_category`) even where the Zscaler API documents camelCase (`customCategory`) — guessing the spelling yields an empty list that looks like a real answer. If you have not already seen a record from this tool, call it once without `query` and read the keys off the response.
searchNo
page_sizeNo
microtenant_idNo
Install Server

TDQS

C2.9/5.0
Behavior2/5

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

The description states 'read-only', but this merely repeats the annotation readOnlyHint=true and adds no new behavioral context. It does not disclose anything about pagination, result structure, or side effects beyond the annotation, so it fails to add value.

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 appropriately terse with no wasted words, but it is under-specified for a tool with multiple parameters and pagination. It is clear but lacks the structural richness needed to guide an agent effectively.

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?

The description fails to explain what the tool returns, how results are paginated, or how to use the filtering parameters. Given the absence of an output schema and the tool's complexity, this is insufficient for reliable invocation.

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

Parameters2/5

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

With only 20% schema description coverage and five parameters, the description provides zero parameter-level guidance. It does not compensate for the low coverage, leaving agents to guess at the meaning and usage of parameters like 'page', 'query', and 'search'.

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 clearly identifies the action (list) and the resource (ZPA isolation policy rules), distinguishing it from the sibling tool zpa_get_isolation_policy_rule which retrieves a single rule. The verb and resource are specific and 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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of filtering, pagination, or any specific context where listing isolation policy rules is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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