Skip to main content
Glama

Standing charges

octopus_get_standing_charges
Read-only

Retrieve a tariff's daily standing charge in pence per day (including VAT) and see changes over a period; choose by tariff code, product code with region/postcode, or current account tariff.

Instructions

Get a tariff's daily standing charge (pence per day, including VAT): the current charge and how it has changed over a period. Choose the tariff by tariff_code, by product_code with region or postcode, or leave them out for the account's current tariff.

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the history (YYYY-MM-DD, inclusive; default today)
fromNoStart of the history to show (YYYY-MM-DD; default 1 year ago)
fuelNoelectricity (default) or gas
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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.6/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 the annotations don't carry: values are VAT-inclusive pence-per-day, the result includes a historical change over a period, and fuel defaults to electricity; it omits any note on failure modes when the tariff/product combination is invalid.

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?

Two sentences, front-loaded with what is returned before the parameter selection rules, with no filler. It is dense but every clause carries information; the second sentence is long but remains readable.

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 9 optional parameters and no output schema, the description does the work of explaining the return shape (current charge plus historical change, in pence/day incl. VAT) and the defaults for the time window are covered by the schema. It is close to complete, missing only guidance on what a valid tariff/product/region combination requires.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning the per-parameter descriptions don't: the three mutually exclusive tariff-selection modes and the fallback to the account's current tariff when all identifiers are omitted. It also clarifies that region/postcode only apply with product_code.

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

Purpose4/5

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

The description states a specific verb and resource ('Get a tariff's daily standing charge') and pins down the unit and basis of the returned value (pence per day, including VAT, current plus change over a period). It does not name a sibling such as octopus_get_unit_rates to draw the contrast explicitly, so it stops short of a 5.

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?

It gives clear conditional guidance for selecting a tariff (by tariff_code, by product_code with region or postcode, or omit for the account's tariff), which tells the agent how to use the tool but not when to prefer it over alternatives. There is no explicit when-not or sibling routing, so usage is implied rather than prescribed.

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