Skip to main content
Glama

parameter_history

Retrieve write and recovery receipts for device parameters, newest first, to audit parameter changes and troubleshoot recovery actions.

Instructions

Retrieve write and recovery receipts, newest first.

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

Input Schema

NameRequiredDescriptionDefault
uriYes
limitNo

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?

With no annotations, the description carries the full behavioral burden, and the only trait it discloses is ordering ("newest first"). It does not say whether this is read-only, whether results are paginated, what a "receipt" record contains, or how the optional limit affects the response.

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?

A single short sentence with no filler, and the ordering note is placed where it is immediately visible. Its brevity is efficient, though it comes at the cost of the missing detail noted elsewhere.

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?

For a tool with no annotations, no output schema, and two undocumented parameters, one sentence is not enough. The definition leaves the meaning of the required uri and the semantics of limit entirely to guesswork, so an agent cannot reliably call it.

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 description says nothing about either parameter. The required "uri" is never explained (target parameter? resource URI?), and "limit" is unmentioned even though its default of 20 shapes the result set.

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 description names a verb ("retrieve") and a resource ("write and recovery receipts"), which suggests a historical log of parameter writes and recoveries. However, "receipts" is unexplained jargon, and the description does not clearly distinguish this from siblings such as read_parameters or apply_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?

It states no condition for when this history should be consulted instead of read_parameters or list_runs. There are no exclusions, prerequisites, or alternative routing hints, so an agent must infer usage from the name alone.

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