Skip to main content
Glama

get_interfaces

Read-onlyIdempotent

Retrieve interface configuration and/or live operational status for a Prisma SD-WAN element, with optional filtering by interface name or ID.

Instructions

Retrieve interface configuration and/or operational state for one element.

If interface is omitted and status is requested, the tool enumerates the element interfaces then fans out to each status endpoint up to the fan-out ceiling (default 100). Individual interface failures remain inline.

Args: element: Element name, serial number, hardware ID, or exact controller ID. If it resolves to exactly one record, site can be omitted — the element's own site is used. site: Site name or controller ID that should own element. Optional when element already resolves uniquely on its own. mode: config returns only interface configuration (no extra API calls). status returns only live operational state per interface. both (default) returns config plus status. interface: Optional filter to one interface by exact ID, exact name (case-insensitive), or name substring. Omit to return every interface on the element. An ambiguous substring returns every candidate rather than guessing. cursor: Opaque pagination token copied from a previous response's next_cursor. Omit on the first call. limit: Max interfaces to return in this page. Omit to use the server default page size (50; max 200).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo`config` returns only interface configuration (no extra API calls). `status` returns only live operational state per interface. `both` (default) returns config plus status.both
siteNoSite name or controller ID that should own `element`. Optional when `element` already resolves uniquely on its own.
limitNoMax interfaces 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.
elementYesElement name, serial number, hardware ID, or exact controller ID. If it resolves to exactly one record, `site` can be omitted — the element's own site is used.
interfaceNoOptional filter to one interface by exact ID, exact name (case-insensitive), or name substring. Omit to return every interface on the element. An ambiguous substring returns every candidate rather than guessing.

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 substantial behavioral traits: fan-out up to a ceiling of 100, inline failure handling, ambiguous substring returning all candidates, pagination via cursor, and exact limit semantics. This goes far beyond what annotations provide.

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 well-structured with a one-sentence summary, a behavioral note, and clear parameter bullets. Despite its length, every sentence adds value and the structure aids comprehension.

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 is remarkably complete for a complex tool: it covers edge cases, pagination, limits, failure behavior, and mode-specific semantics. An output schema exists, so not detailing return structure is acceptable.

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 input schema already covers 100% of parameters with detailed descriptions, so the baseline is 3. The description adds extra context such as the fan-out ceiling and the interaction between interface omission and status mode, so it earns a 4.

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 and resource: 'Retrieve interface configuration and/or operational state for one element.' This clearly distinguishes it from sibling tools like get_routing or get_wan, and the detail about enumerating interfaces and fanning out 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 explains when to use the tool (for interface configuration/state) and describes the modes including when extra API calls occur. It does not explicitly name alternatives or provide when-not-to-use instructions, 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