oegb-kraken-mcp

List energy products

list_products

Read-onlyIdempotent

List Octopus Energy tariff products and return product codes for use with get_product, helping AI agents discover available tariffs without an API key.

Instructions

List Octopus Energy products (tariff families such as Agile, Go, Flexible). Public, no API key needed. Returns product codes to use with get_product.

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

Input Schema

Name	Required	Description
`page`	No	Page number for paginated results (use next_page from the previous call).
`brand`	No	Brand filter, e.g. OCTOPUS_ENERGY.
`is_green`	No
`is_prepay`	No
`is_business`	No
`is_variable`	No
`available_at`	No	Only products available at this datetime (ISO 8601).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds real value beyond that by disclosing that the endpoint is public and requires no API key, which an agent needs before calling. It omits pagination behavior despite the page parameter, keeping it from a 5.

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?

Two tight sentences, front-loading the resource and purpose, followed by the return-value/routing note. There is no filler or redundant restatement of the title.

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?

Covers identity, auth posture, and what is returned, which is a reasonable core. However, for a paginated 7-parameter listing tool with no output schema, the absence of any pagination or filtering guidance leaves a meaningful gap.

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

Parameters2/5

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

With 7 parameters and only 43% schema description coverage, the description should compensate but adds no parameter guidance at all. It never mentions the page parameter, the brand filter, the available_at datetime, or the boolean filter flags, leaving an agent to infer pagination and filtering semantics from bare property names.

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 Octopus Energy products") and clarifies the resource with concrete examples of tariff families (Agile, Go, Flexible). It also distinguishes itself from the sibling get_product by noting it returns product codes used with that tool.

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?

Gives clear context for when to reach for it: it is the public listing call that produces product codes consumed by get_product. It stops short of explicit exclusions (e.g., when to use get_product directly vs. this list, or how to narrow by brand), so it is strong but not complete.

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

Deploy Server