Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

zdx_get_application

Read-only

Get the ZDX score for one application, with its most-impacted regions.

Instructions

Get the ZDX score for one application, with its most-impacted regions.

Read-only. Returns the headline ZDX score plus the per-region impact breakdown for the since HOURS window (default 2h). Use app_id from zdx_list_applications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNo
app_idYes
geo_idNo
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 / app_id / title
      Added value: +"App Id"
    • addedInput schema / properties / department_id / title
      Added value: +"Department 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_applicationArguments"
  2. Changed14 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / app_id / description
      Removed value: -"The unique ID for the ZDX application."
    • removedInput schema / properties / app_id / title
      Removed value: -"App Id"
    • 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 / 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_applicationArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zdx_get_applicationOutput",
-  "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 description adds 'Returns the headline ZDX score plus per-region impact breakdown' and the default time window beyond the annotations' readOnlyHint. However, it does not disclose error handling, pagination, or what happens when filters are applied. With annotations already covering safety, this is a moderate addition.

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?

Three concise, front-loaded sentences. Each sentence adds unique value: purpose, read-only and output details, and parameter sourcing. No redundant or filler content.

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?

The description adequately covers the core output (ZDX score and regional breakdown) and default window, but lacks explanation of the optional filter parameters. Since there is no output schema, the agent must infer the meaning of `geo_id`, `location_id`, and `department_id` from names, which may be insufficient for optimal use.

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%, so the description must compensate. It explains `app_id` (from list) and `since` (hours window), but does not mention `geo_id`, `location_id`, or `department_id`. These optional filters are left undefined, leaving a significant gap for a 5-parameter tool.

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 identifies the tool's purpose: 'Get the ZDX score for one application, with its most-impacted regions.' It specifies the resource (one application) and output (score + region breakdown), distinguishing it from sibling tools like zdx_get_application_metric or zdx_get_application_score_trend.

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 provides concrete guidance by directing users to use `app_id` from `zdx_list_applications` and explaining the `since` window (default 2h). While it doesn't explicitly name alternative tools for other use cases, it gives enough context for an agent to understand when this tool is appropriate (single app score with regional impact).

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