Skip to main content
Glama

Intelligent Octopus dispatches

octopus_get_dispatches
Read-only

Retrieve planned and completed Intelligent Octopus charging dispatches for a car or charger, including scheduled slots and expected energy added, to track smart-charging status.

Instructions

Get Intelligent Octopus charging slots (dispatches) for a car or charger: the planned slots Octopus has scheduled (with the energy each should add) and recent completed slots. On Intelligent Octopus Go, home electricity is charged at the off-peak rate during planned smart-charging slots even outside the usual off-peak hours (Octopus caps how many hours a day this applies to; check your tariff terms). Completed slots are reported about 12 hours late.

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_get_dispatches"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoHow many hours back to include completed dispatches from; fractions allowed (default 24, at most 168). Octopus reports them about 12 hours late
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. Changed2 schema fields changed
    • removedInput schema / properties / completed_hours
      Removed value: -{
      -  "description": "How many hours of completed dispatches to include (default 24, at most 168). Octopus reports them about 12 hours late",
      -  "type": "integer"
      -}
    • addedInput schema / properties / hours
      Added value: +{
      +  "description": "How many hours back to include completed dispatches from; fractions allowed (default 24, at most 168). Octopus reports them about 12 hours late",
      +  "type": "number"
      +}
  2. First observedv0.4.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint false), so the description rightly spends its words on non-obvious behavior: completed slots lag ~12 hours, and planned slots shift home electricity to off-peak rates subject to an hours-per-day cap. It also states what each slot contains (energy added). It stops short of describing ordering or volume of results.

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?

Three sentences, front-loaded with purpose, then payoff semantics, then the latency caveat. The tariff-cap parenthetical is slightly tangential but short and relevant to interpreting planned slots.

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

Completeness4/5

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

No output schema exists, and the description compensates by describing the returned content (planned slots with expected energy, recent completed slots). Given the fully documented schema, little is missing apart from result ordering or pagination.

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 the baseline is 3. The description adds nothing specific about hours, device_id or account_number, though its 'about 12 hours late' remark contextually explains why a short hours window yields few completed slots.

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

Purpose5/5

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

Names a specific verb and resource ('Get Intelligent Octopus charging slots (dispatches) for a car or charger') and enumerates the two result kinds, planned and completed slots. An agent can tell this apart from generic consumption or device-listing tools.

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?

Usage is implied through the tariff explanation and the 'car or charger' scope, and the schema points at octopus_list_devices for device_id. However, there is no explicit statement of when to use this versus octopus_plan_schedule or octopus_get_consumption, and no exclusions.

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