Retrieve the ADC device currently configured for voltage and current sensing.
Get adc_device: ADC device used for voltage/current sensing. [INT8, default: 2]
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_adc_device"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0-alphaDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries full burden for behavioral disclosure. The use of 'Get' implies a read-only operation, but it does not explicitly state that no state is modified, nor does it mention any side effects, authentication needs, or rate limits. For a simple config getter, the implication may suffice, but more explicit transparency would improve clarity.
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 extremely concise, consisting of a single sentence with no unnecessary words. It efficiently communicates the key information: purpose, resource, and additional type/default info.
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?
Given the tool's simplicity (no parameters, no output schema, no annotations), the description is mostly complete. It explains the purpose and includes the type/default. However, it could be improved by specifying the expected output format or units, and by explicitly tying it to its sibling setter tool (set_adc_device) for context.
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 has zero parameters, so the schema provides no parameter-level documentation. The description adds valuable semantic information by indicating the data type (INT8) and default value (2), which are not available from the schema alone. This fully compensates for the lack of parameters.
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 clearly states the tool retrieves the 'adc_device' configuration, which is the ADC device used for voltage/current sensing. This directly distinguishes it from other get_* tools such as get_acc_hardware or get_gyro_hardware, as it specifically targets the ADC device.
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 guidance on when to use this tool versus alternatives (e.g., get_adc_vrefint_calibration or set_adc_device). The description does not mention any prerequisites, context, or exclusions, leaving the agent to infer usage solely from the tool name and brief purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.