zdx_get_analysis

Read-only

Get the status/result of a ZDX score analysis (full record).

Instructions

Get the status/result of a ZDX score analysis (full record).

Read-only. Returns whether the analysis is still running or its results if complete. Start one with zdx_start_analysis.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`analysis_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Analysis result payload, if complete.
`status`	No	Analysis status (running/complete).
`analysis_id`	No	Analysis ID.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.15.3Aug 19, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / analysis_id / title
```
Added value: +"Analysis Id"
```
- addedInput schema / title
```
Added value: +"zdx_get_analysisArguments"
```

Changed13 schema fields changedv0.14.0Jul 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / analysis_id / description
```
Removed value: -"The unique ID for the analysis."
```
removedInput schema / properties / analysis_id / title
```
Removed value: -"Analysis Id"
```

removedInput schema / properties / service

Removed value: -{
-  "default": "zdx",
-  "description": "The service to use.",
-  "title": "Service",
-  "type": "string"
-}

removedInput schema / title

Removed value: -"zdx_get_analysisArguments"

addedOutput schema / additionalProperties
```
Added value: +true
```

addedOutput schema / description

Added value: +"Lean view — a ZDX score-analysis status row."

addedOutput schema / properties / analysis_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Analysis ID.",
+  "title": "Analysis Id"
+}

addedOutput schema / properties / data

Added value: +{
+  "additionalProperties": true,
+  "description": "Analysis result payload, if complete.",
+  "title": "Data",
+  "type": "object"
+}

removedOutput schema / properties / result

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  "title": "Result",
-  "type": "array"
-}

addedOutput schema / properties / status

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Analysis status (running/complete).",
+  "title": "Status"
+}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

changedOutput schema / title

Previous value: -"zdx_get_analysisOutput"New value: +"AnalysisStatus"

First observedv0.12.7Jun 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only'. It adds behavioral context about possible states ('still running or its results if complete'), which is useful beyond the annotations. No contradictions with 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 two sentences with no wasted words. It is front-loaded with the main purpose and provides key details (read-only, status/result, start tool) in a compact form.

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?

With an output schema present, the description need not explain return values. It covers what the tool does, its read-only nature, and how to initiate an analysis. It is sufficiently complete for the tool's simplicity, though it could mention error behavior for invalid IDs.

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 no description for the parameter (0% coverage), and the description does not explicitly explain the analysis_id format or source. However, the parameter name is self-explanatory and the instruction 'Start one with zdx_start_analysis' implies that the ID comes from that call, providing some semantic clues.

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 the status/result of a ZDX score analysis, using a specific verb ('Get') and resource ('ZDX score analysis'). It distinguishes itself from related tools by referencing zdx_start_analysis and noting it returns the 'full record', which differentiates it from other zdx_get_* tools.

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?

The description implies usage after starting an analysis ('Start one with zdx_start_analysis'), providing clear context. It does not explicitly state when not to use it or list alternatives, but the reference to the start tool gives enough guidance for typical use cases.

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

Deploy Server

zscaler-mcp-server