Skip to main content
Glama

get_multicast

Read-onlyIdempotent

Inspect multicast configuration and operational data—rendezvous points, peer groups, routes, IGMP memberships, and WAN status—for Prisma SD-WAN sites and elements.

Instructions

Inspect multicast configuration, RPs, peer groups, routes, IGMP, and WAN status.

Args: operation: Which read to run. No params accepted: peer_groups, routes, igmp_memberships. Requires site only: source_rps, source_site_config. Requires site + element: config, dynamic_rps, rps, protocol_parameters, wan_status. site: Site name or controller ID. Required by the operations listed above; resolved the same way as find_site. Optional narrowing filter for routes/igmp_memberships, which are otherwise tenant-wide. element: Element name or controller ID. Required by the operations listed above; resolved the same way as find_element. Optional narrowing filter for routes/igmp_memberships, and may be combined with site. 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 the operations listed above; resolved the same way as `find_site`. Optional narrowing filter for ``routes``/``igmp_memberships``, which are otherwise tenant-wide.
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 by the operations listed above; resolved the same way as `find_element`. Optional narrowing filter for ``routes``/``igmp_memberships``, and may be combined with `site`.
operationYesWhich read to run. No params accepted: ``peer_groups``, ``routes``, ``igmp_memberships``. Requires ``site`` only: ``source_rps``, ``source_site_config``. Requires ``site`` + ``element``: ``config``, ``dynamic_rps``, ``rps``, ``protocol_parameters``, ``wan_status``.

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, idempotentHint, and safe behavior, so the bar is lower. The description adds useful context about pagination and operation-specific parameter dependencies, which reinforces the tool's read-only nature without contradicting annotations. It doesn't disclose any additional side effects or limitations beyond what schema/annotations imply.

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 clear purpose sentence and a compact parameter list. It is a bit verbose due to repeating schema descriptions, but the operation-grouping summary at the top justifies the length. Every sentence serves a purpose, though some redundancy with schema exists.

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 presence of an output schema and read-only annotations, the description is complete. It explains pagination (cursor, limit), required vs optional arguments per operation, and tenant-wide vs filtered scopes. No critical information is missing for an agent to invoke this tool correctly.

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?

Schema coverage is 100%, and the parameter descriptions in the tool description mostly duplicate schema text. However, the description adds a valuable summary grouping operations by required parameters (e.g., 'Requires site + element: config, dynamic_rps...'), making the dependency structure explicit and easier to parse than the raw schema.

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 verb ('Inspect') and enumerates exact resource categories (multicast config, RPs, peer groups, routes, IGMP, WAN status). This distinguishes it well from sibling tools like get_routing or get_wan, even though it doesn't explicitly name them.

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

Usage Guidelines3/5

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

The description gives precise per-operation parameter requirements, which helps the agent understand internal usage constraints. However, it doesn't explicitly state when to choose this tool over siblings, mention alternatives, or provide exclusion criteria. The guidance is implicit rather than explicit.

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