Skip to main content
Glama

get_identity

Read-onlyIdempotent

Query Prisma SD-WAN directory and tenant identity state: directory service/status, users, groups, active IPs, tenant users, element users, and per-element user access with pagination.

Instructions

Inspect directory/tenant identity state. Session/token fields are always redacted centrally.

Args: operation: Which read to run. No params required: directory_service, directory_status, directory_users, directory_groups, active_user_ips, tenant_users, element_users. Requires object_id: element_user_access. object_id: Element-user ID (from an element_users result's id field). Required only for element_user_access; ignored otherwise. An ID that does not exist is not reported as an error — it returns an empty list, exactly like a valid user with no access records. Confirm the ID came from an element_users result before reading an empty response as "this user has no access". cursor: Opaque pagination token copied from a previous response's next_cursor. Omit on the first call. limit: Max items to return in this page. Omit to use the server default page size (50; max 200).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax items to return in this page. Omit to use the server default page size (50; max 200).
cursorNoOpaque pagination token copied from a previous response's `next_cursor`. Omit on the first call.
detailNo
object_idNoElement-user ID (from an ``element_users`` result's `id` field). Required only for ``element_user_access``; ignored otherwise. An ID that does not exist is **not** reported as an error — it returns an empty list, exactly like a valid user with no access records. Confirm the ID came from an ``element_users`` result before reading an empty response as "this user has no access".
operationYesWhich read to run. No params required: ``directory_service``, ``directory_status``, ``directory_users``, ``directory_groups``, ``active_user_ips``, ``tenant_users``, ``element_users``. Requires ``object_id``: ``element_user_access``.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses key behaviors: session/token fields are always redacted, non-existent object_id returns an empty list rather than an error, and pagination uses an opaque cursor. These are significant behavioral details that an agent needs to interpret results correctly.

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 somewhat long but well-organized with an Args section. The core purpose is front-loaded, and each parameter explanation carries necessary detail. It could be tightened, but the structure makes it scannable. No unnecessary fluff.

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?

For a tool with 5 parameters, 8 enum values, and an output schema, the description covers most operational aspects: redaction, pagination, parameter dependencies, and error semantics. The only clear miss is the 'detail' parameter, which is not mentioned. Overall, it provides sufficient context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the baseline is 3. The description adds valuable nuances for object_id (the empty-list behavior for non-existent IDs) and operation (which operations require object_id), plus pagination semantics for cursor and limit. However, it omits the 'detail' parameter entirely, which appears in the schema with no explanation, leaving a small gap.

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 opens with 'Inspect directory/tenant identity state,' specifying a clear verb and resource. It then enumerates the distinct operations (directory_service, tenant_users, element_user_access, etc.), which distinguishes it from sibling tools like get_inventory or get_routing. The redaction note adds further specificity.

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 clearly states the tool's scope ('directory/tenant identity state') and lists the available operation types, implying when to use it. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of full exclusion guidance.

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/iamdheerajdubey/prisma-sdwan-mcp'

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