Skip to main content
Glama

List Octopus products

octopus_list_products
Read-only

Lists current Octopus Energy tariffs and product codes, including variable, tracker, green, import and export options, so you can identify the right code for price lookups.

Instructions

List the energy products (tariffs) Octopus Energy sells now, such as Agile, Go, Intelligent Go, Cosy, Tracker, Flux, Flexible and fixed deals, with whether each is variable, a tracker, green, import or export. Public data; no account needed. Use the codes with octopus_get_product for prices.

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

Input Schema

NameRequiredDescriptionDefault
brandNoBrand code (default OCTOPUS_ENERGY)
searchNoCase-insensitive filter on the product code and names, for example agile, go, cosy, tracker, flux or fixed
variableNotrue for variable-price products only, false for fixed-price only
directionNoOnly import or export products
available_atNoProducts on sale at this date (YYYY-MM-DD; default now). Use a past date to find products that are no longer sold
include_businessNoInclude business products (default household only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only, closed-world safety profile, and the description adds useful context beyond them: no authentication/account is required, and the result set carries attributes (variable, tracker, green, import/export). It doesn't mention result size or ordering, which is a minor gap for a listing tool.

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

Conciseness5/5

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

Three short sentences with the resource definition first, the access condition second, and the follow-up tool third. Every sentence carries information an agent needs and there is no padding.

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 steps in to say what each product carries (variable/tracker/green/import-export), which is exactly what an agent needs to decide whether to call it. Combined with full schema coverage and annotations, the definition is sufficient, though it could state roughly how many products come back.

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 — brand, search, variable, direction, available_at, include_business — is already documented including the past-date trick. The description adds almost no parameter-level meaning beyond the schema, so the 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?

States a specific verb and resource ("List the energy products (tariffs) Octopus Energy sells now") and enumerates concrete examples (Agile, Go, Cosy, Tracker, Flux) that pin down what a product is here. It also distinguishes itself from octopus_get_product by noting the codes are for use there.

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 the agent to octopus_get_product for prices and states the access condition ("Public data; no account needed"). It lacks an explicit when-not-to-use clause, but the division of labour with the sibling is clear enough to select correctly.

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