Skip to main content
Glama

get_policies

Read-onlyIdempotent

List and inspect Prisma SD-WAN policy sets, stacks, rules, and status across network, priority, NAT, security, or performance families. Provide a policy name or ID to fetch its rules and status.

Instructions

Inspect the major Prisma SD-WAN policy families using human policy names.

sets and stacks can be listed tenant-wide. rules and status require policy as an exact/partial name or ID; ambiguous policy names are never auto-selected. Security policy-set status is not present in the source registry and is therefore reported unsupported instead of invented.

Args: family: Which policy family to inspect: network, priority, nat, security, performance, or all to query every family at once (each item tagged with policy_family). all only supports operation="sets" or "stacks"rules/status need a single policy name, which is meaningless across families at once. operation: sets (default) or stacks list every policy set/stack tenant-wide, no policy needed. rules lists the rules inside one policy set — requires policy. status gets one policy set's status — requires policy; not available for family="security" (reported as unsupported_operation, not guessed). policy: Exact/partial policy-set name or controller ID. Required for rules/status, ignored for sets/stacks. Ambiguous partial matches are never auto-picked — the error lists every candidate so you can retry with an exact name or ID. 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.
familyYesWhich policy family to inspect: `network`, `priority`, `nat`, `security`, `performance`, or `all` to query every family at once (each item tagged with `policy_family`). `all` only supports `operation="sets"` or `"stacks"` — `rules`/`status` need a single `policy` name, which is meaningless across families at once.
policyNoExact/partial policy-set name or controller ID. Required for `rules`/`status`, ignored for `sets`/`stacks`. Ambiguous partial matches are never auto-picked — the error lists every candidate so you can retry with an exact name or ID.
operationNo`sets` (default) or `stacks` list every policy set/stack tenant-wide, no `policy` needed. `rules` lists the rules inside one policy set — requires `policy`. `status` gets one policy set's status — requires `policy`; not available for `family="security"` (reported as `unsupported_operation`, not guessed).sets

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint), the description discloses important behaviors: ambiguous policy names are never auto-selected, errors list candidates, and security policy-set status is reported as unsupported rather than invented. This adds meaningful transparency about edge cases and error handling.

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 well-structured with a summary paragraph and a detailed Args section, making it easy to scan. It is longer than necessary because the Args section duplicates schema descriptions, but every part contributes useful context. The formatting with backticks and line breaks enhances readability.

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

Completeness5/5

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

Given the tool's complexity (5 parameters, multiple operations, cross-parameter constraints), the description is exceptionally complete. It covers all operations, parameter relationships, default behavior, pagination, and unsupported cases. The presence of an output schema further reduces the burden, and the description fills the remaining gaps.

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?

The schema descriptions already cover 100% of parameters, so the baseline is 3. The description's first paragraph adds relational context not fully captured in schema, such as the dependency of rules/status on policy and the limitation of 'all'. However, the Args section largely restates schema descriptions, so the added semantic value is moderate, not exceptional.

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 a clear, specific action: 'Inspect the major Prisma SD-WAN policy families using human policy names.' This distinctly identifies the resource (policy families) and the verb (inspect), and it differentiates the tool from sibling get_* utilities by focusing on policy families and their operations.

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?

Usage guidance is strong: it explains when to use each operation (sets/stacks tenant-wide, rules/status require policy), and explicitly notes that family='all' only supports sets/stacks and that security status is unsupported. However, it does not explicitly name alternative sibling tools for the unsupported cases, so it falls short of a 5.

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