set_powerAdjust motor power (10–100%) to control rover speed; forward drive uses 65% and backward 55% of max 170 px/s.
Set motor power in percent (10–100). Max speed is 170 px/s at 100 % (drive uses 65 % of it forward, 55 % backward).
| Name | Required | Description | Default |
|---|---|---|---|
| percent | Yes |
Changes observed during successful MCP inspections.
v1.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the idempotentHint annotation, the description usefully adds the maximum speed at 100% and the forward/backward drive scaling. However, it does not explain whether this overrides active drive commands, whether motion continues until changed, or how it relates to stop/emergency behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two compact sentences with no wasted text. The core action and valid range are front-loaded, followed by useful speed context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter setter with no output schema, the description covers the essential action, valid range, and physical speed meaning. The main missing context is how this tool relates to sibling motion commands.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must carry meaning. It does so by defining the unit as percent, specifying the 10–100 range, and tying 100% to 170 px/s, though it could clarify integer/decimal expectations or exact directional behavior.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb and resource: 'Set motor power in percent.' It is clear what the tool does, but it does not explicitly distinguish this from sibling movement tools such as drive or turn.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 set_power versus drive, turn, stop, or other motion-related siblings. The percent range is stated, but that is parameter context rather than usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.