Retrieve all Temp Stick sensors available to your API key, including each sensor's latest temperature, humidity, battery level, and offline status for monitoring.
List the Temp Stick sensors visible to your API key, with each sensor's latest temperature, humidity, battery level and offline status.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden, and it does disclose the shape of the data returned (temperature, humidity, battery, offline status) plus the API-key visibility scope. It omits pagination, ordering, and rate-limit behavior, which keeps it short of a 5.
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?
A single sentence that front-loads the action and resource, then the return contents. No filler or redundancy.
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 parameters and no output schema, the description is nearly sufficient: it explains what is returned and the visibility scope. Only minor operational details (ordering, pagination) are absent, which is a small gap for a simple zero-arg list tool.
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 and has an empty object schema, so there is nothing to disambiguate. Baseline 4 applies.
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 ('List the Temp Stick sensors') and scopes it to what the API key can see. It also names the returned fields, which makes it distinguishable from get_sensor, though it doesn't explicitly contrast with that sibling.
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?
Use is implied by 'list the sensors visible to your API key', which suggests a discovery/overview role. There is no explicit statement of when to prefer get_sensor or get_freezer_status over this tool, so an agent must infer the routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.