Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

zms_get_resource_protection_status

Read-only

Get the ZMS resource protection-status summary (curated aggregate view).

Instructions

Get the ZMS resource protection-status summary (curated aggregate view).

Read-only. Returns protected vs unprotected counts and protection percentage — microsegmentation coverage at a glance. Requires ZSCALER_CUSTOMER_ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_numNo
page_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoAggregate payload (counts/percentages).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page_num / title
      Added value: +"Page Num"
    • addedInput schema / properties / page_size / title
      Added value: +"Page Size"
    • addedInput schema / title
      Added value: +"zms_get_resource_protection_statusArguments"
  2. Changed13 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / page_num / description
      Removed value: -"Page number (default 1)."
    • removedInput schema / properties / page_num / title
      Removed value: -"Page Num"
    • removedInput schema / properties / page_size / description
      Removed value: -"Number of items per page (default 20)."
    • removedInput schema / properties / page_size / title
      Removed value: -"Page Size"
    • removedInput schema / properties / service
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "The service to use.",
-  "title": "Service"
-}
    • removedInput schema / title
      Removed value: -"zms_get_resource_protection_statusArguments"
    • addedOutput schema / additionalProperties
      Added value: +true
    • addedOutput schema / description
      Added value: +"Aggregate ZMS status/metadata payload — kept nested."
    • addedOutput schema / properties / data
      Added value: +{
+  "additionalProperties": true,
+  "description": "Aggregate payload (counts/percentages).",
+  "title": "Data",
+  "type": "object"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  "title": "Result",
-  "type": "array"
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"zms_get_resource_protection_statusOutput"New value: +"AggregateStatus"
  3. First observedv0.12.7

TDQS

A3.9/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 valuable context beyond annotations: the return content (protected vs unprotected counts, protection percentage) and the auth requirement (ZSCALER_CUSTOMER_ID). It does not contradict 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 three short sentences, front-loaded with the core purpose and followed by essential return-value and auth context. Every sentence earns its place with no filler.

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?

Given the output schema exists and annotations cover safety, the description is largely complete: it states the return summary, read-only nature, and required customer ID. The main gap is the absence of pagination semantics, but this is a simple read-only summary tool, so the overall context is sufficient.

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 mention page_num or page_size at all. While the parameter names and defaults are self-explanatory, the description fails to compensate for the low schema coverage or clarify how pagination affects the aggregate summary.

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 uses a specific verb ('Get') and names a precise resource ('ZMS resource protection-status summary'), with 'curated aggregate view' clarifying the scope. This distinguishes it from the sibling zms_get_resource_group_protection_status, which targets resource groups rather than the overall summary.

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 'microsegmentation coverage at a glance' implies a quick-summary use case, but the description does not explicitly state when to prefer this over alternatives or when not to use it. No exclusions or alternative tool references are provided.

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