Skip to main content
Glama

read_parameters

Retrieves a device's current effective parameter values so you can verify settings after adjustments or experiments.

Instructions

Read back the device's current effective values.

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": "read_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden and it discloses almost no behavior: it does not say whether values are read live from hardware or from a cached config, whether "effective" means post-override values, what permissions or connection state are needed, or what happens on failure. Only the read-only nature is inferable from "read back."

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?

One short, front-loaded sentence with no filler or redundancy. Its brevity is efficient, though it shades into under-specification rather than tightness.

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?

With no annotations, no output schema, and a 0%-documented required parameter, the description leaves too much unstated for even a simple read tool. An agent knows the intent but not the target resource type, prerequisites, or return shape.

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

Parameters2/5

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

Schema description coverage is 0% and the sole required parameter, `uri`, is never mentioned in the description. The agent must guess whether the URI identifies a device, a parameter set, or a config resource, so the description 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.

Purpose4/5

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

The description pairs a specific verb ("read back") with a concrete resource ("the device's current effective values"), so an agent knows this is a live-state read of parameters. The word "parameters" itself comes only from the tool name, and nothing distinguishes it from the sibling parameter_history, which plausibly returns the same values over time.

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 when-to-use guidance, no prerequisite such as an active run or connected device, and no routing to alternatives like parameter_history or describe. Usage is only weakly implied by the phrase "current effective values."

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