Skip to main content
Glama

apply_parameters

Set bounded temporary parameter values on embedded devices and read them back to verify changes, returning previous, applied, and verified values.

Instructions

Apply bounded temporary values and read back. Returns previous, applied and independently verified 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>",
      "values": "<values>"
    },
    "name": "apply_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYes
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that values are temporary and bounded, that it reads back, and that it returns previous, applied, and independently verified values, but it omits permissions, side effects, duration, reversibility, and failure behavior.

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 two sentences, front-loaded with the action, and contains no filler. Both sentences contribute useful information without repetition.

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 mutation-style tool with no annotations, no output schema, and zero schema description coverage, the description is too thin. It should explain the target (uri), value keys, permissions, temporary lifetime, and what 'bounded' and 'independently verified' mean in practice.

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%, so the description must compensate. It adds some meaning to 'values' by calling them bounded and temporary, but it never explains the 'uri' parameter or clarifies that 'values' is a mapping of parameter names to numbers.

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 states a specific action ('Apply') and mentions reading back, but 'bounded temporary values' is vague and does not identify the target resource or distinguish this tool from siblings like read_parameters or parameter_history.

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 explicit guidance on when to use this tool versus alternatives such as read_parameters or parameter_history. The phrase 'temporary values' hints at a use case but does not provide actionable selection criteria or exclusions.

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