zscaler-mcp-server

Official

by zscaler

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

zins_get_shadow_it_apps

Read-only

Get discovered Shadow IT applications with risk and usage detail. Read-only analytics.

Instructions

Get discovered Shadow IT applications with risk and usage detail. Read-only analytics.

One row per unsanctioned/discovered app: category, risk index, sanctioned state, data volume, and user count. An empty result means no shadow apps were detected. Window must be a 7- or 14-day historical interval.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	No	Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: "[?enabled==`true`]", "[*].{name: name, id: id}", "length(@)". Omit to get the full records. IMPORTANT: field names are the keys of the returned records, which are usually snake_case (`custom_category`) even where the Zscaler API documents camelCase (`customCategory`) — guessing the spelling yields an empty list that looks like a real answer. If you have not already seen a record from this tool, call it once without `query` and read the keys off the response.
`end_time`	No
`start_time`	No
`end_days_ago`	No
`start_days_ago`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.15.3Aug 19, 2026

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 / limit / title
```
Added value: +"Limit"
```

changedInput schema / properties / query / description

Previous value: -"Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Field names are exactly what the Zscaler API returns. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records."New value: +"Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records. IMPORTANT: field names are the keys of the returned records, which are usually snake_case (`custom_category`) even where the Zscaler API documents camelCase (`customCategory`) — guessing the spelling yields an empty list that looks like a real answer. If you have not already seen a record from this tool, call it once without `query` and read the keys off the response."

addedInput schema / properties / query / title
```
Added value: +"Query"
```
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_appsArguments"

Changed14 schema fields changedv0.14.0Jul 28, 2026

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 / limit / description

Removed value: -"Maximum number of application entries to return (1-1000)."

removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```

addedInput schema / properties / query

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Field names are exactly what the Zscaler API returns. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records."
+}

removedInput schema / properties / start_days_ago / description

Removed value: -"Days ago for start. Default: 9 (7-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_appsArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zins_get_shadow_it_appsOutput",
-  "type": "object"
-}New value: +null

First observedv0.12.7Jun 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With readOnlyHint=true in annotations, the description adds value beyond annotations by explaining the empty-result interpretation and the time-window constraint. It doesn't delve into pagination or limit behavior, but the key behavioral nuances are covered.

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 front-loaded: two sentences plus a brief output-format line. Every sentence adds meaningful information without fluff. Ideal length for a tool description.

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 covers the purpose, output format, empty-result semantics, and a key constraint, but lacks information on limit behavior, how to interpret risk/usage fields, and the relationship between start_days_ago and end_days_ago. Given the low schema coverage and no output schema, more detail on parameters and result interpretation would make it complete.

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?

Schema coverage is only 17% (only query has a description). The description compensates partially by noting the 7/14-day window which directly relates to time parameters, but it does not explain limit, start_time, or end_time. The query parameter is fully documented in the schema, so the description adds minimal value for that. Overall, only partial compensation for low coverage.

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 'Get discovered Shadow IT applications with risk and usage detail' and specifies the row-level output fields. It distinguishes from sibling 'zins_get_shadow_it_summary' by focusing on detailed per-app analytics rather than aggregation.

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?

Provides clear context: read-only analytics, empty result meaning, and the required 7- or 14-day window. However, it does not explicitly compare to alternative tools (e.g., when to use this vs. summary) or mention any exclusions, so it's slightly incomplete.

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

Deploy Server

zins_get_shadow_it_apps

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools