Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

zpa_get_application_server

Read-only

Fetch a single ZPA application server's details by ID. Use this read-only operation to retrieve its configuration.

Instructions

Get one ZPA application server (read-only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_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 / microtenant_id / title
      Added value: +"Microtenant Id"
    • addedInput schema / properties / server_id / title
      Added value: +"Server Id"
    • addedInput schema / title
      Added value: +"zpa_get_application_serverArguments"
  2. Changed8 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • 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 / server_id / description
      Removed value: -"Server ID for the application server."
    • removedInput schema / properties / server_id / title
      Removed value: -"Server 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_application_serverArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zpa_get_application_serverOutput",
-  "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 says 'read-only,' but that merely repeats what the annotations already provide via readOnlyHint=true. It adds no additional behavioral details such as not-found handling, response shape, microtenant scoping, or any operational caveats, so it adds little beyond the structured 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?

The description is a single short sentence that front-loads the key action and resource. Every word earns its place, with no fluff or unnecessary repetition.

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 operation, the description is minimally viable, especially with readOnlyHint provided and the schema naming the required parameter. However, it lacks any output shape hints, parameter semantics, or explicit usage guidance, leaving meaningful gaps for the agent.

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 explain server_id or microtenant_id. The connection between 'get one application server' and server_id is inferable, but the optional microtenant_id parameter and its purpose are completely unexplained, so the description fails to compensate for the missing schema documentation.

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 is specific and action-oriented: 'Get one ZPA application server' clearly identifies the resource and the singular retrieval. It distinguishes this from the sibling list operation zpa_list_application_servers by emphasizing 'one'.

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 phrase 'Get one' implies a singular lookup versus a list operation, and sibling tools like zpa_list_application_servers suggest the alternative. However, the description does not explicitly state when to use this tool or provide any exclusion or preference guidance.

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