zscaler-mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

get_zpa_trusted_network

Read-only

Retrieve ZPA trusted networks and look them up by ID or name. Supports pagination and JMESPath expressions to filter and project results.

Instructions

List ZPA trusted networks, or look one up by ID or name (read-only).

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`page`	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.
`page_size`	No
`network_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.15.3Aug 19, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / name / title
```
Added value: +"Name"
```
addedInput schema / properties / network_id / title
```
Added value: +"Network Id"
```

addedInput schema / properties / page

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Page"
+}

addedInput schema / properties / page_size

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Page Size"
+}

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: +"get_zpa_trusted_networkArguments"

Changed16 schema fields changedv0.14.0Jul 28, 2026

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

removedInput schema / properties / action

Removed value: -{
-  "description": "Action to perform. Must be 'read'.",
-  "title": "Action",
-  "type": "string"
-}

addedInput schema / properties / name / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / name / description

Removed value: -"If provided, will be used to search for the trusted network."

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

addedInput schema / properties / network_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / network_id / description

Removed value: -"If provided, retrieves trusted network by ID."

removedInput schema / properties / network_id / title
```
Removed value: -"Network Id"
```
removedInput schema / properties / network_id / type
```
Removed value: -"string"
```

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 / query_params

Removed value: -{
-  "additionalProperties": true,
-  "default": null,
-  "description": "Optional query parameters for filtering results.",
-  "title": "Query Params",
-  "type": "object"
-}

removedInput schema / properties / service

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

removedInput schema / required
```
Removed value: -[
-  "action"
-]
```

removedInput schema / title

Removed value: -"trusted_network_managerArguments"

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": "trusted_network_managerOutput",
-  "type": "object"
-}New value: +null

First observedv0.12.7Jun 24, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description adds the capability of looking up by ID or name beyond annotations. Annotations already specify read-only, and the description repeats that, which is redundant. It does not disclose pagination or return format, but with readOnlyHint true and no contradictory info, this is adequate.

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?

A single, concise sentence that immediately conveys the main actions. No filler, and the read-only note is useful. Perfectly sized.

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?

With 5 parameters and no output schema, the description is insufficient. It only covers list vs lookup but leaves pagination, query semantics, and parameter purposes unexplained. The absence of an output schema increases the need for description to indicate what is returned, which it does not do. Incomplete for a tool of this complexity.

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?

Schema description coverage is only 20% (query param). The description hints that name and network_id are used for lookup, but does not explain page, page_size, or the query behavior. It does not compensate for the low coverage; the agent would need to rely on bare parameter names. The query param has its own detailed description, but that's not part of the tool's 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 it lists ZPA trusted networks or looks one up by ID or name. This is a specific verb+resource and distinguishes the tool from others targeting different resource types (e.g., rules, segments). Comprehensive enough for the agent to understand the primary actions.

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?

It clarifies the two modes (list all vs. look up by ID/name), making it evident when to use this tool. It does not explicitly mention alternatives or exclusions, but the sibling tools are for different resource types, so the niche is clear. A more explicit 'use list for all, lookup for specific' would be better, but the context is sufficient.

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

Deploy Server

get_zpa_trusted_network

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools