Skip to main content
Glama
iamdheerajdubey

Prisma SD-WAN MCP Server

by iamdheerajdubey
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

list_capabilities

Read-onlyIdempotent

Discover available Prisma SD-WAN API capabilities by browsing domains and actions, filtering by HTTP method, and retrieving full execution contracts for any action to run it.

Instructions

Browse the v2 capability catalog when no semantic tool fits the request.

This is the discovery companion to read_capability. Normal operator workflows should prefer semantic tools. Call with no arguments to list every domain and its action count. Call again with domain set to one of the returned identifiers to list every action in that domain. Browsing a domain returns what you need to choose an action; ask for one action_id to get the full execution contract needed to run it. Nothing is ever truncated at either step.

Args: domain: A domain identifier returned by a prior no-argument call (e.g. "sites_devices", "security_policies"). Omit to list every domain instead of one domain's actions. method: Filter one domain's actions to only "GET" or only "POST". Ignored (and has no effect) when domain is omitted. action_id: An exact action identifier. Returns that one action's full contract — path_parameters, body_schema, output_fields, api_version — which is what read_capability needs. Use this after browsing a domain; domain and method are ignored when it is set. detail: Applies to a domain listing. "compact" (default) returns action_id, http_method, description, any required path parameters, and whether the action takes a body — enough to pick one. "full" returns every action's complete contract in one response, which for a large domain is several times bigger.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detailNoApplies to a domain listing. ``"compact"`` (default) returns ``action_id``, ``http_method``, ``description``, any required path parameters, and whether the action takes a body — enough to pick one. ``"full"`` returns every action's complete contract in one response, which for a large domain is several times bigger.
domainNoA domain identifier returned by a prior no-argument call (e.g. ``"sites_devices"``, ``"security_policies"``). Omit to list every domain instead of one domain's actions.
methodNoFilter one domain's actions to only ``"GET"`` or only ``"POST"``. Ignored (and has no effect) when `domain` is omitted.
action_idNoAn exact action identifier. Returns that one action's full contract — ``path_parameters``, ``body_schema``, ``output_fields``, ``api_version`` — which is what ``read_capability`` needs. Use this after browsing a domain; `domain` and `method` are ignored when it is set.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations already establish read-only and idempotent behavior. The description adds valuable context: 'Nothing is ever truncated at either step' and the parameter precedence rules for ignored arguments. This goes well beyond the structured annotations.

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 one-sentence summary, a usage workflow paragraph, and a detailed Args block. It is somewhat long and the Args section duplicates the schema, but the added precedence information and examples justify the length.

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?

The description fully covers the discovery workflow, output expectations at each step, and edge cases (ignored parameters, large domain responses). With an output schema present, the description's level of detail is sufficient for a capable agent to invoke the tool correctly.

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

Parameters5/5

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

Schema descriptions match the Args section, but the description adds examples (sites_devices, security_policies) and clarity about parameter interactions and ignored-argument precedence. It describes the effect of 'detail' on response size, which is not evident from the schema alone.

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 specific verb+resource: 'Browse the v2 capability catalog when no semantic tool fits the request.' It explicitly names read_capability as its companion and explains the browse→select→read workflow, distinguishing it from semantic tools and read_capability.

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

Usage Guidelines5/5

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

It provides explicit guidance: 'Normal operator workflows should prefer semantic tools' and positions this tool as a discovery fallback. It also explains when to call with no args, with domain, and with action_id, and notes that method is ignored when domain is omitted, and domain/method are ignored when action_id is set.

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