Skip to main content
Glama

get_inventory

Read-onlyIdempotent

Retrieve sites, ION elements, hardware, or applications from Prisma SD-WAN inventory. Use search, summary or full detail, and pagination to get exactly the operational data you need.

Instructions

Retrieve core Prisma SD-WAN inventory with compact operator-oriented output.

kind selects sites, ION elements, hardware machines, or application definitions. Summary mode projects the fields most useful for reasoning; full mode preserves the redacted controller record and should be used with a search/limit for large collections.

Args: kind: Inventory collection to retrieve: sites, elements (IONs), machines (hardware), or applications. Use find_site/find_element/find_resource instead if you already know a name and just need to resolve it to an ID. search: Case-insensitive substring filter across name, display_name, description, id, serial_number, and hw_id. Omit to return the whole collection (subject to limit). detail: summary (default) projects only the most relevant fields for reasoning. full returns the complete redacted controller record per item — use with search or a tight limit for large collections (e.g. applications can be thousands of rows). Note: kind="applications" with no search and detail="summary" ignores pagination and instead returns one aggregate summary (total_applications + counts per category), not a row list. 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
kindYesInventory collection to retrieve: `sites`, `elements` (IONs), `machines` (hardware), or `applications`. Use `find_site`/`find_element`/`find_resource` instead if you already know a name and just need to resolve it to an ID.
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`summary` (default) projects only the most relevant fields for reasoning. `full` returns the complete redacted controller record per item — use with `search` or a tight `limit` for large collections (e.g. `applications` can be thousands of rows). Note: `kind="applications"` with no `search` and `detail="summary"` ignores pagination and instead returns one aggregate summary (`total_applications` + counts per category), not a row list.summary
searchNoCase-insensitive substring filter across name, display_name, description, id, serial_number, and hw_id. Omit to return the whole collection (subject to `limit`).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds significant behavioral detail: summary vs full mode, pagination tokens, redacted controller records, and the special aggregate summary for applications without search. These are meaningful operational nuances beyond the structured fields.

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 an introductory sentence followed by a clear Args list. It is somewhat long but every sentence conveys relevant information, with no fluff or redundancy beyond the unavoidable repetition of schema details.

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 params, multiple modes, large collections), the description covers all key operational aspects: pagination, output modes, collection-specific behavior, and alternatives. An output schema exists, so detailed return values are not needed in the description.

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?

The schema description coverage is 100% and the tool description's Args section essentially duplicates the schema parameter descriptions. No additional meaning is provided beyond what the schema already contains, so the baseline of 3 applies.

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 states a specific verb and resource: 'Retrieve core Prisma SD-WAN inventory.' It also distinguishes itself from sibling tools by noting 'Use find_site/find_element/find_resource instead if you already know a name and just need to resolve it to an ID.' This clearly frames the tool's scope as broad inventory retrieval rather than targeted name-based lookups.

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?

Explicit guidance is given on when to use alternatives: 'Use find_site/find_element/find_resource instead if you already know a name...' Additionally, it advises using search/limit for large collections and notes the aggregate behavior for applications, giving clear situational context.

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