Skip to main content
Glama

Find the greenest times

octopus_find_greener_slots
Read-only

Find lower-carbon electricity times over the next 48 hours, compare tariff prices, and choose continuous blocks or half-hour slots for planned usage.

Instructions

Find the lowest-carbon times to use electricity in your region over the next 48 hours, from the official regional carbon intensity forecast of NESO (Great Britain's electricity system operator, api.carbonintensity.org.uk), alongside your tariff's prices: the greenest continuous block of a given length, runner-up blocks, the greenest half-hours, the cheapest block for comparison, and the intensity now. Intensity is grams of CO2 per kWh of electricity generated in the region (a forecast), with NESO's index from very low to very high. The region comes from the tariff, or from region or postcode on their own (then without prices). Choose the tariff by tariff_code, by product_code with region or postcode, or leave them out for the account's current tariff. Northern Ireland isn't covered.

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

Input Schema

NameRequiredDescriptionDefault
toNoLatest end: a date and time, or a date (inclusive; default as far as the forecast goes, about 48 hours ahead)
kwhNoEnergy the job will use, in kWh, to estimate its emissions (and cost, when prices are known) in each block
fromNoEarliest start: a date and time, or now (default now)
fuelNoelectricity (default) or gas
slotsNoAlso list this many of the lowest-carbon individual half-hours (default 6; 0 for none)
regionNoWith product_code: the region letter A to P (see octopus_find_region)
postcodeNoWith product_code, instead of region: a UK postcode, used to look up the region
directionNoWith the account's tariff: import (default) or export
tariff_codeNoA tariff code like E-1R-AGILE-24-10-01-C (from octopus_get_product or octopus_get_account)
product_codeNoInstead of tariff_code: a product code like AGILE-24-10-01 (see octopus_list_products), with region or postcode
account_numberNoWith none of the above, the account's current tariff is used: account number like A-1234ABCD (default OCTOPUS_ACCOUNT or the only account)
duration_hoursNoLength of the continuous block to find, in hours, in steps of 0.5 (default 2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds meaningful context beyond them: the upstream source (api.carbonintensity.org.uk), that values are a forecast, the units (gCO2/kWh) and NESO's very-low-to-very-high index, and the geographic exclusion. It does not explain why results are non-idempotent (forecast refresh), which would have closed the loop on the remaining annotation.

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?

The purpose and outputs are front-loaded in the first sentence, followed by the supporting definitions of intensity, region resolution, and tariff selection. It is dense and reads as one long run-on paragraph, but nearly every clause carries information an agent needs; the loss is in scannability rather than wasted words.

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?

With 12 optional parameters and no output schema, the description does the necessary work of enumerating the returned artifacts and defining the intensity metric and its index. The main remaining gap is the shape and ordering of the returned blocks (e.g., how runner-up blocks are ranked or labeled), which an agent must discover at call time.

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 every parameter is already documented, and the description largely restates the same selection logic (tariff_code vs product_code plus region/postcode, region from postcode). It adds framing about what duration_hours and kwh are for (block length and emissions/cost estimation) but no syntax or format detail beyond the schema. Baseline 3 applies.

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?

The description opens with a specific verb and resource ('Find the lowest-carbon times to use electricity in your region over the next 48 hours') and enumerates exactly what is returned: the greenest continuous block, runner-up blocks, greenest half-hours, the cheapest block for comparison, and current intensity. It is clearly distinguishable from octopus_find_cheapest_slots because it names its data source (NESO carbon intensity forecast) and its carbon-first framing.

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

Usage Guidelines4/5

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

It gives explicit routing rules for tariff selection (tariff_code, product_code plus region/postcode, or neither for the account's current tariff) and explains that region alone yields results without prices. It also states a scope exclusion ('Northern Ireland isn't covered'). It stops short of an explicit when-to-use-this-vs-octopus_find_cheapest_slots statement, leaving that inference to the reader.

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