Skip to main content
Glama

set_param

Change one navigation parameter of a robot, such as goal tolerance, inflation radius, or max speed, to adjust how that simulated warehouse robot navigates.

Instructions

Change one navigation parameter of a robot.

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": {
      "robot_id": "<robot_id>",
      "name": "<name>",
      "value": "<value>"
    },
    "name": "set_param"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
valueYes
robot_idYesRobot id, e.g. amr_1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the write-and-not-idempotent nature is covered structurally. The description adds nothing beyond that: it doesn't say whether the change persists across restarts, applies immediately, requires the robot to be idle, or affects an active navigation goal — all material for a mutation on a moving robot.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is good structurally. However, the brevity comes at the cost of under-specification rather than genuine density — there is room to add value without bloat.

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 three-required-parameter mutation tool with no output schema and only a partial schema description, the agent is left without confirmation of what the call returns, whether the change persists, or what failure modes exist. Existing annotations cover only the safety profile, so the description should carry more of the behavioral load than it does.

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 only 33% (just robot_id), and the enum on 'name' enumerates the allowed parameters. The description adds only the notion that a single parameter is changed at a time; it says nothing about valid ranges, units, or what happens to 'value' for a parameter like max_speed, so it does not compensate for the coverage gap.

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?

States a specific verb ('Change'), resource ('navigation parameter'), and scope ('one ... of a robot'), which the agent can distinguish from the read-only get_params sibling. It stops short of naming any sibling explicitly, so the differentiation is implied rather than stated.

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?

The description gives no when-to-use guidance, no when-not-to-use conditions, and never points to get_params for reading current values or to any alternative for bulk/other parameter types. The only hint is the word 'Change', which contrasts implicitly with a read.

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