Skip to main content
Glama

Get product and prices

octopus_get_product
Read-only

Retrieve an Octopus Energy product's details and current regional prices, including VAT, unit rates, standing charges, and exit fees for electricity and gas.

Instructions

Get an Octopus product's details and its current prices in each region, including VAT: unit rate (pence per kWh; day and night rates for Economy 7), standing charge (pence per day) and any exit fee, for electricity and gas. For half-hourly tariffs such as Agile the unit rate shown is only indicative; use octopus_get_unit_rates. Public data; no account needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_code": "<product_code>"
    },
    "name": "octopus_get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoShow the prices in force at this date (YYYY-MM-DD; default now)
rawNoReturn the API response unchanged
regionNoOnly show tariffs for this region letter, A to P (default all regions)
postcodeNoInstead of region: a UK postcode, used to look up the region
product_codeYesProduct code, like AGILE-24-10-01 or VAR-22-11-01 (see octopus_list_products)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: prices include VAT, unit rates are pence per kWh, half-hourly rates are only indicative, data is public, and the date defaults to now (consistent with idempotentHint=false since prices change over time). It does not describe the response shape or what the `raw` flag changes behaviorally, so it adds value but not a rich behavioral picture.

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?

Front-loaded with the core verb and resource, then the return contents, then the sibling disambiguation and the auth note; every sentence carries information. The first sentence is dense with nested parentheses, which slightly hurts scannability but not content value.

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 no output schema, the description carries the burden of explaining return values and does so by listing unit rate, standing charge, and exit fee with units. The only remaining gap is the behavior of the `raw` parameter output mode, which is left entirely to the schema.

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 all five parameters, including region, postcode, at, and raw, are already documented in the schema and the baseline of 3 applies. The description reinforces that prices are per-region and current, but adds no syntax, format, or precedence detail beyond what the schema states.

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?

States a specific verb+resource (product details and current prices) and enumerates the returned price components: unit rate in pence per kWh with Economy 7 day/night split, standing charge pence per day, and exit fee, for both electricity and gas. It also distinguishes itself from octopus_get_unit_rates for half-hourly tariffs, so an agent can pick between them without opening schemas.

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?

Explicitly routes half-hourly/Agile queries to octopus_get_unit_rates and notes that no account is required, which tells the agent this is safe, unauthenticated lookup. It does not explicitly say when to prefer octopus_get_standing_charges (a sibling) over this broader call, but the inclusion of standing charge here implies the relationship.

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