Skip to main content
Glama

describe

Retrieves firmware identity, signal units, parameters, permitted actions, conditions, and metrics for a device URI so you can inspect supported capabilities.

Instructions

Discover firmware identity, signal units, parameters, permitted actions, conditions and metrics.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uri": "<uri>"
    },
    "name": "describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Discover' implies a read operation, but the description does not explicitly state read-only/side-effect-free behavior, permission requirements, error handling, or what happens if the URI is invalid. The enumerated output categories are useful but do not substitute for behavioral context.

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 definition is a single front-loaded sentence with no filler, so it is appropriately concise. The flat list of attributes is somewhat unstructured, but the wording itself is efficient.

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

Completeness2/5

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

Given no annotations, no output schema, and a required 'uri' parameter with 0% schema coverage, the description should define the target resource and input format. It only lists output categories and leaves the core input and behavioral contract unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the only parameter, 'uri', is never mentioned in the description. The description does not say what the URI identifies, what format it takes, or why it is required. It adds no meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Discover' is specific enough, and the sentence enumerates the metadata categories returned: firmware identity, signal units, parameters, permitted actions, conditions, and metrics. However, it never names the resource being described or connects those categories to the required 'uri' argument, so the purpose remains only partially clear. It also does not distinguish this tool from siblings such as 'devices' or 'read_parameters'.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool instead of siblings, what kind of URI is acceptable, or what prerequisites exist. An agent must infer everything from the tool name and the bare schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.