Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

zins_get_shadow_it_summary

Read-only

Get the aggregate Shadow IT summary dashboard. Read-only analytics.

Instructions

Get the aggregate Shadow IT summary dashboard. Read-only analytics.

A single object with org-wide totals (apps, bytes, upload/download) plus breakdowns grouped by category and by risk index. Window must be a 7- or 14-day historical interval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_timeNo
start_timeNo
end_days_agoNo
start_days_agoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / end_days_ago / title
      Added value: +"End Days Ago"
    • addedInput schema / properties / end_time / title
      Added value: +"End Time"
    • addedInput schema / properties / start_days_ago / title
      Added value: +"Start Days Ago"
    • addedInput schema / properties / start_time / title
      Added value: +"Start Time"
    • addedInput schema / title
      Added value: +"zins_get_shadow_it_summaryArguments"
  2. Changed11 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / end_days_ago / description
      Removed value: -"Days ago for end. Default: 2. Interval = start - end must be 7 or 14."
    • removedInput schema / properties / end_days_ago / title
      Removed value: -"End Days Ago"
    • removedInput schema / properties / end_time / description
      Removed value: -"ALTERNATIVE: End time as Unix epoch in MILLISECONDS."
    • removedInput schema / properties / end_time / title
      Removed value: -"End Time"
    • removedInput schema / properties / start_days_ago / description
      Removed value: -"Days ago for start. Default: 16 (14-day interval). API needs 7 or 14 day intervals."
    • removedInput schema / properties / start_days_ago / title
      Removed value: -"Start Days Ago"
    • removedInput schema / properties / start_time / description
      Removed value: -"ALTERNATIVE: Start time as Unix epoch in MILLISECONDS."
    • removedInput schema / properties / start_time / title
      Removed value: -"Start Time"
    • removedInput schema / title
      Removed value: -"zins_get_shadow_it_summaryArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zins_get_shadow_it_summaryOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.12.7

TDQS

A4.3/5.0
Behavior5/5

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

The description explicitly states 'Read-only analytics' matching the readOnlyHint annotation. It also describes the output shape and the window limitation, adding behavioral context beyond the annotations. No contradictions.

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 concise and efficient, using three short sentences. It front-loads the main verb ('Get') and then adds supporting details. No redundant words or 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?

The description covers the essential aspects: what it returns, the read-only nature, and the time interval constraint. However, it does not explain the individual parameters or their default behavior, which could leave some uncertainty. Overall adequate for a simple read operation, but not fully complete.

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?

The schema has 0% coverage for parameters (no descriptions). The description mentions a 'Window must be a 7- or 14-day historical interval,' which loosely relates to the time parameters but does not explain the meaning or usage of start_time, end_time, start_days_ago, or end_days_ago. This is insufficient given the lack of schema descriptions.

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's purpose: 'Get the aggregate Shadow IT summary dashboard' with details on what it returns (org-wide totals, breakdowns by category and risk index). It distinguishes itself from sibling tools by focusing on summary analytics, not listing specific apps or detailed reports.

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 provides a clear usage constraint: the window must be a 7- or 14-day historical interval. It also implies when to use this tool (for aggregate summaries) but does not explicitly mention alternatives or exclusions. Still, the interval constraint gives practical guidance.

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