Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

zdx_get_device

Read-only

Get one active ZDX device.

Instructions

Get one active ZDX device.

Read-only. The ZDX SDK returns a single-element list; the device record is unwrapped and shaped to the identifying fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNo
geo_idNo
device_idYes
location_idNo
department_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / department_id / title
      Added value: +"Department Id"
    • addedInput schema / properties / device_id / title
      Added value: +"Device Id"
    • addedInput schema / properties / geo_id / title
      Added value: +"Geo Id"
    • addedInput schema / properties / location_id / title
      Added value: +"Location Id"
    • addedInput schema / properties / since / title
      Added value: +"Since"
    • addedInput schema / title
      Added value: +"zdx_get_deviceArguments"
  2. Changed14 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / department_id / description
      Removed value: -"Filter by department ID(s)."
    • removedInput schema / properties / department_id / title
      Removed value: -"Department Id"
    • removedInput schema / properties / device_id / description
      Removed value: -"The unique ID for the ZDX device."
    • removedInput schema / properties / device_id / title
      Removed value: -"Device Id"
    • removedInput schema / properties / geo_id / description
      Removed value: -"Filter by geolocation ID(s)."
    • removedInput schema / properties / geo_id / title
      Removed value: -"Geo Id"
    • removedInput schema / properties / location_id / description
      Removed value: -"Filter by location ID(s)."
    • removedInput schema / properties / location_id / title
      Removed value: -"Location Id"
    • removedInput schema / properties / service
      Removed value: -{
-  "default": "zdx",
-  "description": "The service to use.",
-  "title": "Service",
-  "type": "string"
-}
    • removedInput schema / properties / since / description
      Removed value: -"Number of hours to look back (default 2h)."
    • removedInput schema / properties / since / title
      Removed value: -"Since"
    • removedInput schema / title
      Removed value: -"zdx_get_deviceArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zdx_get_deviceOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.12.7

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description repeats 'Read-only' which adds no new info. However, it does disclose that the SDK returns a single-element list which gets unwrapped, and that the device is 'active' (a filtering behavior). These are useful beyond annotations, but still limited.

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?

Two sentences with no fluff. The purpose is directly stated first, followed by a concise behavioral note. No redundancy or extra detail.

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?

The description does not explain the 5 parameters, lacks an output schema, and omits error scenarios or prerequisites. While read-only and unwrapping are mentioned, the tool still leaves the agent guessing about optional filters and response structure.

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 provides no parameter explanations. Only the tool name implies device_id is the identifier; the four optional parameters (since, geo_id, location_id, department_id) are left undefined. The description fails to compensate for the schema gap.

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 tool 'Gets one active ZDX device' with the verb 'get' and specific resource 'ZXD device', distinguishing it from list tools. It also notes the response is a single unwrapped device record, which clarifies the output.

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

Usage Guidelines2/5

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

The description does not provide any guidance on when to use this tool versus alternatives (e.g., zdx_list_devices) or mention exclusions. It implies a single-device lookup but lacks explicit 'use case' instructions.

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