zscaler-mcp-server

Official

by zscaler

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

zia_list_gre_ranges

Read-only

List available ZIA GRE internal-IP ranges.

Instructions

List available ZIA GRE internal-IP ranges.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	No	Optional 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.
`static_ip`	No
`internal_ip_range`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.15.3Aug 19, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / internal_ip_range / title
```
Added value: +"Internal Ip Range"
```
addedInput schema / properties / limit / title
```
Added value: +"Limit"
```

changedInput schema / properties / query / description

Previous value: -"Optional 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."New value: +"Optional 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."

addedInput schema / properties / query / title
```
Added value: +"Query"
```
addedInput schema / properties / static_ip / title
```
Added value: +"Static Ip"
```

addedInput schema / title

Added value: +"zia_list_gre_rangesArguments"

Changed12 schema fields changedv0.14.0Jul 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / internal_ip_range / description

Removed value: -"CIDR range filter (e.g., '172.17.47.247-172.17.47.240')."

removedInput schema / properties / internal_ip_range / title
```
Removed value: -"Internal Ip Range"
```
removedInput schema / properties / limit / description
```
Removed value: -"Max number of ranges to return."
```
removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```

changedInput schema / properties / query / description

Previous value: -"JMESPath expression for client-side filtering/projection of results."New value: +"Optional 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."

removedInput schema / properties / query / title
```
Removed value: -"Query"
```

removedInput schema / properties / service

Removed value: -{
-  "default": "zia",
-  "description": "The service to use.",
-  "title": "Service",
-  "type": "string"
-}

removedInput schema / properties / static_ip / description

Removed value: -"Filter by the associated static IP address."

removedInput schema / properties / static_ip / title
```
Removed value: -"Static Ip"
```

removedInput schema / title

Removed value: -"zia_list_gre_rangesArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "items": {},
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zia_list_gre_rangesOutput",
-  "type": "object"
-}New value: +null

First observedv0.12.7Jun 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. However, the description adds no behavioral context beyond that, such as pagination defaults, rate limits, or the structure of the response. For a list operation with a query parameter that has a critical caveat (field naming), the description does not surface any of these nuances.

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, efficient sentence that states the action and object. It is front-loaded and contains no redundant content. It is appropriately sized for a simple list operation.

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 4 optional parameters, no output schema, and limited annotations, the description is too sparse. It does not explain the parameters (beyond the query field's schema description), nor does it provide examples or note the response shape. The description is incomplete for an agent to use it effectively without prior knowledge.

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 25% (only the query parameter has a description). The tool description does not explain any parameters, and the other three (limit, static_ip, internal_ip_range) remain undocumented. With low coverage, the description was expected to compensate but does not. The detailed query description in the schema is helpful but not part of the tool description.

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 states the verb (List) and the resource (ZIA GRE internal-IP ranges). It distinguishes from sibling tools like zia_list_gre_tunnels, which lists tunnels not internal-IP ranges, and other list tools.

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. It does not mention related tools, prerequisites, or typical use cases. The description is purely functional without contextual direction.

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

Deploy Server

zia_list_gre_ranges

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools