Skip to main content
Glama

get_cellular

Read-onlyIdempotent

Retrieve cellular module details, firmware status, APN profiles, and module images from Prisma SD-WAN devices. Supports filtering by element or machine and pagination.

Instructions

Inspect cellular modules, firmware status, APN profiles, and module images.

Args: operation: Which read to run. No params required: module_images, apn_profiles, firmware_status. Requires machine: machine_modules. Requires element: modules (the default cellular-module read). element: Element name, serial number, hardware ID, or controller ID. Required only for modules; resolved the same way as find_element. machine: Machine name, hardware ID, serial number, or controller ID. Required only for machine_modules; resolved the same way as find_resource(kind="machine"). 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
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
elementNoElement name, serial number, hardware ID, or controller ID. Required only for ``modules``; resolved the same way as `find_element`.
machineNoMachine name, hardware ID, serial number, or controller ID. Required only for ``machine_modules``; resolved the same way as `find_resource(kind="machine")`.
operationYesWhich read to run. No params required: ``module_images``, ``apn_profiles``, ``firmware_status``. Requires ``machine``: ``machine_modules``. Requires ``element``: ``modules`` (the default cellular-module read).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context such as pagination via cursor/limit and operation-specific parameter requirements. It does not contradict annotations, and the added details are valuable.

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: a one-line summary followed by a concise Arg list with each parameter explained in a compact format. The most important context is front-loaded, and every sentence provides necessary information without redundancy.

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 all operation variants, required vs optional parameters, pagination behavior, and resolution semantics. Since an output schema exists, the lack of return-value details is acceptable. The tool is complex with 6 parameters and 5 operation modes, yet the description handles it comprehensively.

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 83%, and the description largely repeats the property descriptions already present in the schema. For instance, the 'operation' and 'element' descriptions are nearly identical. No new semantic meaning is added, so the baseline score of 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 cellular modules, firmware status, APN profiles, and module images,' which is a specific verb and resource. It clearly differentiates this tool from sibling tools like get_interfaces or get_wan by focusing on cellular-specific data.

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 Args section explicitly explains which operations require no parameters, which require 'machine', and which require 'element', providing clear usage context. However, it does not mention alternatives or exclusions relative to sibling tools, 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