Skip to main content
Glama

get_prisma_access

Read-onlyIdempotent

Retrieve Prisma Access/SASE integration, connections, prefixes, and ADEM state to troubleshoot and verify network operations.

Instructions

Inspect Prisma Access/SASE integration, connections, prefixes, and ADEM state.

Args: operation: Which read to run. Requires site: site_config, connections, adem_site_config, adem_status. Requires site + object_id: connection_status (a SASE connection ID from a connections result's id field). No params required: connection_config, pa_networks, integration_status. Requires site + element: advertised_prefixes, reachable_prefixes. site: Site name or controller ID. Required by most operations (see operation); resolved the same way as find_site. element: Element name or controller ID. Required only for the prefix operations; resolved the same way as find_element. object_id: SASE connection ID. Required only for connection_status; ignored otherwise. 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
siteNoSite name or controller ID. Required by most operations (see `operation`); resolved the same way as `find_site`.
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.
elementNoElement name or controller ID. Required only for the prefix operations; resolved the same way as `find_element`.
object_idNoSASE connection ID. Required only for ``connection_status``; ignored otherwise.
operationYesWhich read to run. Requires ``site``: ``site_config``, ``connections``, ``adem_site_config``, ``adem_status``. Requires ``site`` + ``object_id``: ``connection_status`` (a SASE connection ID from a ``connections`` result's `id` field). No params required: ``connection_config``, ``pa_networks``, ``integration_status``. Requires ``site`` + ``element``: ``advertised_prefixes``, ``reachable_prefixes``.

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, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds pagination behavior (cursor/limit) and notes that object_id is ignored for non-status operations, but these details are also present in the schema. No extra behavioral context such as auth or rate limits is provided, but there is no contradiction with annotations.

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?

The description is front-loaded with a clear purpose, followed by a structured Args list that methodically covers six parameters. Despite its length, every sentence earns its place given the tool's 10 operation variants and dependent parameters. No redundant or vague phrasing.

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 (10 operations, 6 parameters, interdependencies), the description fully covers parameter requirements, pagination, and operation variants. An output schema is present, so return-value documentation isn't needed. The description is complete for understanding this tool's behavior, even though sibling differentiation is handled elsewhere.

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?

Schema description coverage is 100%, and the description's Args section largely mirrors the schema's property descriptions. It adds minimal new meaning beyond organizing the operation-dependent requirements, which is already in the schema. Thus, the baseline 3 is appropriate.

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 Prisma Access/SASE integration, connections, prefixes, and ADEM state,' which is a specific verb ('Inspect') tied to a concrete resource domain. This clearly distinguishes it from sibling tools like get_routing or get_inventory, which target different resources. The operation enum further specifies the exact reads supported.

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 explains which operation requires which parameters and mentions that some operations need no params, giving clear usage context. However, it does not explicitly state when to use this tool instead of siblings or when to prefer an alternative, so it stops 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