Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

zpa_get_server_group

Read-only

Retrieve details for a specific ZPA server group by its ID, optionally scoped to a microtenant, for read-only access.

Instructions

Get one ZPA server group (read-only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYes
microtenant_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / group_id / title
      Added value: +"Group Id"
    • addedInput schema / properties / microtenant_id / title
      Added value: +"Microtenant Id"
    • addedInput schema / title
      Added value: +"zpa_get_server_groupArguments"
  2. Changed8 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / group_id / description
      Removed value: -"Group ID for the server group."
    • removedInput schema / properties / group_id / title
      Removed value: -"Group Id"
    • removedInput schema / properties / microtenant_id / description
      Removed value: -"Microtenant ID for scoping."
    • removedInput schema / properties / microtenant_id / title
      Removed value: -"Microtenant Id"
    • removedInput schema / properties / service
      Removed value: -{
-  "default": "zpa",
-  "description": "The service to use.",
-  "title": "Service",
-  "type": "string"
-}
    • removedInput schema / title
      Removed value: -"zpa_get_server_groupArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zpa_get_server_groupOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.12.7

TDQS

B3.4/5.0
Behavior2/5

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

The description merely repeats the read-only hint already present in annotations and adds no extra behavioral context—no return shape, error semantics, authentication requirements, or microtenant scope behavior.

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 brief sentence is tightly front-loaded and conveys action, resource, and scope with zero filler.

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 read-only get-by-id tool this is minimally viable, but with no output schema or parameter descriptions, it leaves return-value shape and microtenant semantics unexplained.

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 0%, and the description does not compensate by explaining the role of group_id or microtenant_id beyond their self-evident names and schema titles.

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?

Description uses a specific verb ('Get'), names the resource ('ZPA server group'), and signals singular scope ('one'), clearly distinguishing it from zpa_list_server_groups and other ZPA get/list siblings.

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?

'Get one' implies this is for retrieving a single group by ID when the caller knows which group is needed, but the description never explicitly contrasts it with zpa_list_server_groups or states exclusions.

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

Deploy Server

Other Tools