Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler

get_zia_user_departments

Read-only

Retrieve ZIA user departments to view organizational structure. Supports pagination, search, sorting, and filtering by department ID.

Instructions

Manage ZIA user departments for organizational structure (read-only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoOperation to perform. Use 'read' to paginate/filter departments, 'read' to fetch a department by ID, or 'read_lite' for the lite version.read
department_idNoDepartment ID. Required for 'read' and 'read_lite' actions.
limit_searchNoIf true, limits the search to match against the department name only.
searchNoSearch string to match against department name or user attributes.
pageNoPage offset for pagination when listing departments.
page_sizeNoPage size for listing departments. Default is 100; maximum is 1000.
sort_byNoSort field for listing departments.
sort_orderNoSort order for listing departments.
serviceNoZscaler service name. Always 'zia' for this tool.zia

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description confirms read-only behavior. No additional behavioral traits (e.g., rate limits, authentication needs, side effects) are disclosed. Since the annotation covers safety, a score of 3 is appropriate as the description adds minimal extra value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very brief (one line) and front-loads the purpose. It is concise but lacks structure; a slightly more detailed explanation could improve clarity without harming conciseness.

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?

Given the tool is read-only, has full schema coverage, and an output schema exists, the description could be considered adequate but minimal. It does not explain pagination or sort behavior beyond the schema, and it lacks usage context. Overall, it meets minimum requirements but has gaps.

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 input schema has 100% description coverage for its 9 parameters, so the schema already provides parameter meanings. The description does not add any extra parameter semantics beyond the schema. Baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Manage ZIA user departments for organizational structure (read-only)', which clearly indicates it retrieves department information. The verb 'Manage' is slightly misleading given the read-only nature, but the parenthetical clarifies. The tool name directly implies the purpose, and the description is sufficient for basic understanding.

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 is provided on when to use this tool versus alternatives like 'zdx_list_departments' or other list/get tools for ZIA. There is no mention of prerequisites, contexts, or exclusions. The description lacks any usage differentiation.

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