Skip to main content
Glama

List smart devices

octopus_list_devices
Read-only

Lists the devices Octopus controls for smart tariffs, including cars, chargers, batteries and heat pumps, with make, model, status, smart charging suspension, battery level and charging schedule.

Instructions

List the devices Octopus controls for smart tariffs such as Intelligent Octopus Go: electric cars, chargers, batteries and heat pumps, with each one's make and model, status (for example SMART_CONTROL_CAPABLE, BOOSTING or LOST_CONNECTION), whether smart charging is suspended, battery level where reported, and its charging schedule (target charge and ready-by time for each day).

Tool call template

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": "octopus_list_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_idNoThe device's ID from octopus_list_devices (default: the account's only car or charger)
account_numberNoAccount number like A-1234ABCD (default OCTOPUS_ACCOUNT, or the only account the API key can see)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so the safety profile is covered by structured data and the description needn't restate it. Beyond that, the text only enumerates return fields and never says whether large device lists are paginated or truncated, whether an account with no smart devices returns an empty list or an error, or what authentication/scope is required; for a read tool with no output schema the return-shape detail is useful, but operational behavior is left undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the verb and resource, with the returned-field enumeration placed after the core purpose. It is dense but every clause carries information; the only inefficiency is that the field list grows long for a single sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must convey what comes back, and it does list make/model, status values, suspension state, battery level and schedule. It remains incomplete on the two optional parameters' behavior (omitting device_id to get all devices) and on empty-result handling, which an agent needs before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both optional parameters are already fully documented in the schema, including their defaults. The description adds no meaning about device_id or account_number, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('List the devices Octopus controls for smart tariffs') and enumerates the device categories (cars, chargers, batteries, heat pumps), so the scope is unambiguous. It stops short of naming a distinguishing alternative such as octopus_get_dispatches or octopus_get_octoplus, which is why it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The mention of 'smart tariffs such as Intelligent Octopus Go' implies the context in which this tool applies, and the schema notes the defaults for device_id and account_number. There is, however, no explicit statement of when to prefer this tool over sibling lookups, no exclusions, and no prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.