Samples servo-rail current for a set duration and returns peak, mean, and minimum mA, so you can check current draw and detect overcurrent conditions.
Sample the servo-rail current continuously; returns peak, mean and min mA.
| Name | Required | Description | Default |
|---|---|---|---|
| seconds | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden; it does disclose the sampling mode ('continuously') and the return statistics, which is genuine behavioral value. However, it omits whether the call blocks for the sampling window, sampling rate, error/overflow behavior, or permission requirements.
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?
One front-loaded sentence with no filler, but it is arguably too terse for a tool whose only parameter and blocking behavior need explaining.
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?
Reasonable for a single-parameter tool with no output schema, since the description covers the return statistics. Still missing the meaning/units of 'seconds' and how long the call actually takes, which an agent needs to invoke it correctly.
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% for the single 'seconds' parameter (default 1), and the description never mentions a duration argument at all — 'continuously' only weakly implies a sampling window. The description fails to compensate for the undocumented parameter.
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?
States a specific verb and resource ('Sample the servo-rail current') and describes the return payload (peak, mean, min mA). It is distinguishable from generic siblings like read_analog, though it never names them.
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?
No indication of when to use this versus read_analog, nor any prerequisite such as servos needing to be enabled or the port being open. Usage is only implied by the tool name and 'continuously'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.