Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler

get_zpa_saml_attribute

Read-only

List ZPA SAML attributes for an IdP, with optional search, pagination, and query filtering. Retrieve read-only SAML attribute data from Zscaler for inspection or further processing.

Instructions

List ZPA SAML attributes, optionally scoped to a named IdP (read-only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
queryNoOptional 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.
searchNo
idp_nameNo
page_sizeNo
Install Server

TDQS

A3.5/5.0
Behavior3/5

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

The read-only nature is already declared in annotations and repeated in the description. The description adds the optional IdP scoping behavioral detail, but does not mention pagination, search behavior, or potential error conditions. Given the annotation covers safety, score is moderate.

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?

A single sentence that front-loads the main action and scope, with no wasted words. Perfectly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 5 parameters, no output schema, and limited schema descriptions. The description only covers the IdP scoping, leaving 'search' and pagination behavior unexplained. This makes it incomplete for an agent to fully understand the tool's capabilities and limitations.

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 only 20% (only 'query' has a description). The description adds meaning for 'idp_name' via 'scoped to a named IdP', but fails to clarify 'search', 'page', or 'page_size'. Since low coverage requires the description to compensate, this is insufficient.

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 action ('List ZPA SAML attributes') and adds optional scoping to an IdP. This distinguishes it from sibling tools like get_zpa_scim_attribute and get_zpa_scim_group.

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 description implies use for listing SAML attributes with optional IdP scoping, but does not provide explicit when-to-use vs alternatives or exclusions. It lacks a direct comparison to sibling tools such as get_zpa_scim_attribute.

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

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