Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

zia_get_static_ip

Read-only

Get a single ZIA static IP by ID.

Instructions

Get a single ZIA static IP by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
static_ip_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / static_ip_id / title
      Added value: +"Static Ip Id"
    • addedInput schema / title
      Added value: +"zia_get_static_ipArguments"
  2. Changed7 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / service
      Removed value: -{
-  "default": "zia",
-  "description": "The service to use.",
-  "title": "Service",
-  "type": "string"
-}
    • removedInput schema / properties / static_ip_id / description
      Removed value: -"Static IP ID."
    • removedInput schema / properties / static_ip_id / title
      Removed value: -"Static Ip Id"
    • changedInput schema / properties / static_ip_id / type
      Previous value: -"integer"New value: +"string"
    • removedInput schema / title
      Removed value: -"zia_get_static_ipArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zia_get_static_ipOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.12.7

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already indicates a safe read operation, and the description ('Get') is consistent. No additional behavioral context (e.g., side effects, authentication needs) is provided beyond the annotation, but there is no contradiction.

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, concise sentence with no redundant words or unnecessary details. It is perfectly sized for the tool's simplicity.

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

Completeness4/5

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

The tool is a simple get-by-ID operation with one parameter and no output schema. The description sufficiently conveys the purpose and input, and the returned data is implicitly the static IP object. It is adequate for the context.

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?

The schema has one parameter, static_ip_id, which is self-explanatory given the description's 'by ID' phrase. The description does not add further detail about the parameter, but the coverage is high, so the baseline of 3 applies.

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 the action ('Get') and the resource ('single ZIA static IP') with the identifier ('by ID'), distinguishing it from list operations like zia_list_static_ips. It is specific and unambiguous.

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 description implies use when a specific static IP ID is known, but it does not explicitly contrast with the list alternative or provide any when/when-not guidance. The context of sibling tools suggests the distinction, but it is not stated.

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