Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler

zins_get_threat_class

Read-only

Retrieve threat classification analytics with breakdowns by virus, trojan, ransomware, and other malware types for a specified time range.

Instructions

Provides detailed threat classification analytics including virus, trojan, ransomware, and other malware type breakdowns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_days_agoNoDays ago for start. Default: 9 (7-day interval). API needs 7 or 14 day intervals.
end_days_agoNoDays ago for end. Default: 2. Interval = start - end must be 7 or 14.
start_timeNoALTERNATIVE: Start time as Unix epoch in MILLISECONDS.
end_timeNoALTERNATIVE: End time as Unix epoch in MILLISECONDS.
traffic_unitNoTraffic measurement unit. Values: TRANSACTIONS, BYTESTRANSACTIONS
limitNoMaximum number of threat class entries to return (1-1000).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already indicate readOnlyHint=true, so the read-only nature is clear. The description adds no further behavioral context (e.g., rate limits, auth requirements). Adequate but not enhanced.

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?

Single sentence, no filler, front-loaded with actionable information. Very concise.

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, return values are documented. Description summarizes purpose well. Could mention time-range aspect from parameters but still complete enough.

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 covers all 6 parameters with descriptions. The description adds no additional parameter insights beyond the schema. Baseline score appropriate.

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 it provides threat classification analytics with specific examples (virus, trojan, ransomware), distinguishing it from sibling tools like zins_get_threat_super_categories.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as zins_get_cyber_incidents or other threat analytics tools. Missing context for appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zscaler/zscaler-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server