Read battery voltage, current draw, consumed mAh, and RSSI from a Betaflight flight controller. Use it to monitor power status during telemetry checks or tuning.
Tension batterie (V), courant (A), mAh consommés, RSSI
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond the unit annotations (V, A) and unitless fields like mAh and RSSI — nothing about freshness, sampling, or error states.
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?
It is a single compact fragment with zero filler and the payload fields are front-loaded. It is arguably too terse rather than bloated, so it is efficient but not exemplary.
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?
With no output schema, the description usefully enumerates the returned fields (voltage, current, mAh, RSSI), which is the main value it adds. However, for a telemetry tool sitting among many similar battery/meter siblings, the absence of any selection guidance leaves the definition only minimally complete.
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?
The tool takes zero parameters, so the baseline is 4. The description correctly implies a plain parameterless read, and there is nothing for it to document or mis-document.
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 lists the telemetry it returns (voltage, current, mAh consumed, RSSI) but uses no verb and never states that the tool retrieves/reads this data. It also fails to differentiate from close siblings such as get_battery_state, get_voltage_meters, and get_current_meters, which appear to overlap in scope.
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 when-to-use guidance, no conditions, and no mention of alternatives. An agent cannot tell from this text why it would call get_battery rather than get_battery_state or the individual meter tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.