Skip to main content
Glama

get_platform

Read-onlyIdempotent

Inspect tenant and platform metadata, licenses, SKUs, machines, and reports. Query machine system status and software versions, with sensitive values redacted before returning.

Instructions

Inspect tenant/platform metadata, licenses, SKUs, machines, and reports.

Sensitive values in external CA or other returned objects are recursively redacted before leaving the server.

Args: operation: Which read to run. No params required: tenant, licenses, skus, machines, external_ca, otp_access, hub_service_endpoints. Requires machine: machine_system_status, machine_software. reports takes no parameters — see folder. machine: Machine name, hardware ID, serial number, or controller ID. Required only for the two machine-scoped operations; resolved the same way as find_resource(kind="machine"). folder: Not usable. The endpoint ignores it — every value returns zero items, including a folder path copied verbatim from an unfiltered reports result — so passing it is rejected with a 400 rather than returning a misleading empty list. Call reports unfiltered and select from the returned path/type fields yourself. 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
folderNoNot usable. The endpoint ignores it — every value returns zero items, including a folder `path` copied verbatim from an unfiltered ``reports`` result — so passing it is rejected with a 400 rather than returning a misleading empty list. Call ``reports`` unfiltered and select from the returned `path`/`type` fields yourself.
machineNoMachine name, hardware ID, serial number, or controller ID. Required only for the two machine-scoped operations; resolved the same way as `find_resource(kind="machine")`.
operationYesWhich read to run. No params required: ``tenant``, ``licenses``, ``skus``, ``machines``, ``external_ca``, ``otp_access``, ``hub_service_endpoints``. Requires ``machine``: ``machine_system_status``, ``machine_software``. ``reports`` takes no parameters — see `folder`.

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 reveals a recursive redaction of sensitive values and the specific 400-rejection behavior for the `folder` parameter. It also documents pagination semantics (cursor/limit), giving the agent expectations for server behavior that are not derivable from the schema alone.

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 front-loaded with a one-sentence purpose and a clear 'Args:' list. However, the parameter explanations repeat the schema descriptions nearly verbatim, adding length. The structure is good but the redundancy prevents a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description covers operation modes, parameter requirements, pagination, and error behavior. The only notable gap is the unexplained `detail` parameter, and the interplay between `reports` and the (rejected) `folder` is clarified. Overall, this is strong for a multi-mode tool.

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 already describes most parameters (83% coverage) with detailed explanations, and the description largely duplicates those descriptions. It adds no substantive new meaning for parameters beyond the schema, though the redaction note is globally relevant. The `detail` parameter is left unexplained in both description and 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 verb ('Inspect') and enumerates the resource categories ('tenant/platform metadata, licenses, SKUs, machines, and reports'), distinguishing it from sibling tools focused on network or device-specific reads. The operation parameter further enumerates 10 distinct read modes, making the tool's scope concrete.

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?

It identifies which operations require the `machine` parameter, states that `reports` takes no parameters, and explicitly warns that `folder` is rejected. It references `find_resource` for machine resolution, providing a cross-tool cue, but it does not explicitly state when to prefer this tool over sibling tools (e.g., `get_software` vs `machine_software`).

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