Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

zia_list_network_services

Read-only

List ZIA network services with support for case-insensitive name matching, protocol filtering, and JMESPath queries to fetch service details.

Instructions

List ZIA network services (read-only). Pass name="<friendly admin-supplied name>" (e.g. name="http", name="ftp", name="dns") for a case-insensitive substring match resolved client-side — this is the right knob when the admin gives a service name in any casing. ZIA's canonical service names are uppercase enums (HTTP, FTP, DNS, ...), so server-side search is case-sensitive and unreliable for friendly inputs. Also supports protocol / locale filters and JMESPath projection via query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoCase-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).
searchNoServer-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.
protocolNoFilter by protocol. Supported values: 'ICMP', 'TCP', 'UDP', 'GRE', 'ESP', 'OTHER'.
localeNoLocale for localized descriptions. Supported: 'en-US', 'de-DE', 'es-ES', 'fr-FR', 'ja-JP', 'zh-CN'.
queryNoJMESPath expression for client-side filtering/projection of results.
serviceNoThe service to use.zia

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true; description adds significant behavioral context: client-side resolution for 'name' (fetch full catalog, then filter), server-side case-sensitive behavior for 'search', support for protocol/locale filters and JMESPath projection. No contradiction with annotations.

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?

Front-loaded with the core purpose, then efficiently expands on the most important parameter (name) with actionable guidance. Every sentence adds value—no waste. Length is appropriate given the complexity of the different filter behaviors.

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

Completeness5/5

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

With an output schema present, the description need not cover return values. It covers all key behaviors: read-only, client-side/server-side filtering distinctions, available filters, and JMESPath projection. An agent has enough information to select and invoke the tool correctly.

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

Parameters5/5

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

Schema coverage is 100%, but description goes far beyond: explains the critical client-side vs server-side distinction for name/search with concrete examples, lists supported values for protocol and locale, describes JMESPath projection scope. Adds meaning that the schema alone does not convey.

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 starts with a specific verb+resource ('List ZIA network services (read-only)') and immediately distinguishes itself from sibling 'get' tools (e.g., get_zia_network_service) by being a list operation. It explicitly mentions the read-only nature, which aligns with annotations.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use the 'name' parameter vs 'search': 'name' for case-insensitive substring match resolved client-side, 'search' for server-side case-sensitive lookup. Includes examples ('http', 'HTTP', 'Http') and warns about unreliability of server-side search for friendly inputs. Gives clear context for each filter option.

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