zscaler-mcp-server

Official

by zscaler

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

zia_list_network_services

Read-only

List ZIA network services. Use name for case-insensitive find-by-name.

Instructions

List ZIA network services. Use name for case-insensitive find-by-name.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	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.
`search`	No
`protocol`	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 / name / title
```
Added value: +"Name"
```
addedInput schema / properties / protocol / title
```
Added value: +"Protocol"
```

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

addedInput schema / title

Added value: +"zia_list_network_servicesArguments"

Changed13 schema fields changedv0.14.0Jul 28, 2026

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

removedInput schema / properties / locale

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Locale for localized descriptions. Supported: 'en-US', 'de-DE', 'es-ES', 'fr-FR', 'ja-JP', 'zh-CN'.",
-  "title": "Locale"
-}

removedInput schema / properties / name / description

Removed value: -"Case-insensitive substring match on the network service's `name` field. Resolved client-side AFTER fetching the full service catalog, so 'http', 'HTTP', and 'Http' all match the predefined `HTTP` service. Use this when the admin gives a literal service name in any casing (e.g. 'http', 'ftp', 'dns') and you just need to find its ID. Recommended for find-by-name workflows over `search` (which is server-side and case-sensitive against the canonical uppercase names)."

removedInput schema / properties / name / title
```
Removed value: -"Name"
```

removedInput schema / properties / protocol / description

Removed value: -"Filter by protocol. Supported values: 'ICMP', 'TCP', 'UDP', 'GRE', 'ESP', 'OTHER'."

removedInput schema / properties / protocol / title
```
Removed value: -"Protocol"
```

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 / search / description

Removed value: -"Server-side query forwarded to the ZIA list_network_services endpoint. Matches against name and description, but is effectively case-sensitive against ZIA's canonical uppercase service names — so `search='http'` will NOT match the predefined `HTTP` service. Prefer `name` for case-insensitive lookups; use `search` only when you need server-side semantics."

removedInput schema / properties / search / title
```
Removed value: -"Search"
```

removedInput schema / properties / service

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

removedInput schema / title

Removed value: -"zia_list_network_servicesArguments"

changedOutput schema / (root)

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

First observedv0.12.7Jun 24, 2026

TDQS

A3.5/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 read-only safety profile is known. The description adds the case-insensitive behavior of the name parameter, which is useful context beyond the annotations. However, it doesn't disclose return format, pagination, or how search/protocol affect results.

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?

Two short sentences with zero waste. The purpose is front-loaded ('List ZIA network services') and the parameter hint is placed immediately after. Every word earns its place.

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

Completeness3/5

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

For a simple list tool with 0 required params, the core purpose is covered. However, with no output schema and two undocumented params (search, protocol), the description could be more complete. The schema's detailed `query` documentation helps, but the tool still has gaps in parameter coverage and return-value disclosure.

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 description coverage is low (25% — only `query` is documented in the schema). The description compensates partially by noting `name` enables case-insensitive find-by-name, adding meaning beyond the bare schema entry. However, `search` and `protocol` remain completely undocumented in both schema and description, leaving a significant semantic gap.

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 states the tool action clearly: 'List ZIA network services' — a specific verb and resource. The second sentence adds the find-by-name capability. It doesn't explicitly distinguish from siblings like zia_list_network_svc_groups or zia_get_network_service, but the ZIA scope and 'list' vs 'get' verb provide implicit differentiation.

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

Usage Guidelines3/5

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

The instruction 'Use `name` for case-insensitive find-by-name' implies when to use the name parameter, providing some usage context. However, there is no explicit when-to-use vs alternatives, no exclusions, and no guidance on how this tool relates to zia_get_network_service or zia_list_network_svc_groups among the many sibling list tools.

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_network_services

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools