zscaler-mcp-server

Official

by zscaler

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

zia_geo_search

Read-only

Resolve ZIA geo data by coordinates, by IP, or by city prefix (read-only).

Instructions

Resolve ZIA geo data by coordinates, by IP, or by city prefix (read-only).

Input Schema

TableJSON Schema

Name	Required	Description
`ip`	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.
`action`	Yes
`prefix`	No
`latitude`	No
`longitude`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.15.3Aug 19, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / action / title
```
Added value: +"Action"
```
addedInput schema / properties / ip / title
```
Added value: +"Ip"
```
addedInput schema / properties / latitude / title
```
Added value: +"Latitude"
```
addedInput schema / properties / longitude / title
```
Added value: +"Longitude"
```
addedInput schema / properties / prefix / title
```
Added value: +"Prefix"
```

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 / title
```
Added value: +"zia_geo_searchArguments"
```

Changed15 schema fields changedv0.14.0Jul 28, 2026

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

removedInput schema / properties / action / description

Removed value: -"Choose one of: geo_by_coordinates, geo_by_ip, city_prefix_search"

removedInput schema / properties / action / title
```
Removed value: -"Action"
```

removedInput schema / properties / ip / description

Removed value: -"Required if action is geo_by_ip"

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

removedInput schema / properties / latitude / description

Removed value: -"Required if action is geo_by_coordinates"

removedInput schema / properties / latitude / title
```
Removed value: -"Latitude"
```

removedInput schema / properties / longitude / description

Removed value: -"Required if action is geo_by_coordinates"

removedInput schema / properties / longitude / title
```
Removed value: -"Longitude"
```

removedInput schema / properties / prefix / description

Removed value: -"Required if action is city_prefix_search"

removedInput schema / properties / prefix / title
```
Removed value: -"Prefix"
```

addedInput schema / properties / query

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "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 / service

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

removedInput schema / title

Removed value: -"zia_geo_search_toolArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "anyOf": [
-        {
-          "additionalProperties": true,
-          "type": "object"
-        },
-        {
-          "items": {
-            "additionalProperties": true,
-            "type": "object"
-          },
-          "type": "array"
-        },
-        {
-          "type": "string"
-        }
-      ],
-      "title": "Result"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zia_geo_search_toolOutput",
-  "type": "object"
-}New value: +null

First observedv0.12.7Jun 24, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=false, so the safety profile is declared. The description adds the three lookup modes (coordinates, IP, city prefix) which is useful behavioral context beyond annotations, but does not disclose return format, pagination, or potential errors.

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, front-loaded sentence with zero fluff. It conveys the core purpose and three modes efficiently, earning every word.

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 tool has 6 parameters and 3 distinct actions, yet the description is sparse. It does not explain which parameters are required for each action, nor does it describe the output shape or error behavior. The schema only explains 'query', leaving most parameters undocumented. While the read-only annotation covers safety, a multi-mode tool like this needs more explicit guidance for correct invocation.

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?

Schema coverage is only 17% (only 'query' has a full description). The tool description hints at parameter usage via the three modes (coordinates -> latitude/longitude, IP -> ip, city prefix -> prefix), but it does not explicitly map each action to required fields. The 'query' parameter description in the schema is comprehensive, but the tool description itself adds minimal semantic detail.

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 tool resolves ZIA geo data via three distinct modes (coordinates, IP, city prefix) and explicitly labels it read-only. It uses a specific verb 'Resolve' and resource 'ZIA geo data', distinguishing it from the many sibling list/get tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool (for geo resolution needs) and its read-only nature, but does not explicitly name alternatives or exclusions. However, given the sibling tool set, this is the only geo lookup tool, so context is clear enough.

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

Deploy Server

zia_geo_search

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools