Skip to main content
Glama

List transactions

octopus_list_transactions
Read-only

List an Octopus Energy account’s transactions newest first, including charges, payments, credits and refunds in pounds with the balance after each. Filter by date range, limit and account number.

Instructions

List the account's transactions, newest first: charges for energy, payments (such as direct debits), credits (such as Octoplus rewards or Saving Session payouts) and refunds, in pounds, with the balance after each.

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

Input Schema

NameRequiredDescriptionDefault
toNoOnly transactions posted on or before this date (YYYY-MM-DD)
fromNoOnly transactions posted on or after this date (YYYY-MM-DD)
limitNoHow many to return, newest first (default 20, at most 99)
account_numberNoAccount number like A-1234ABCD (default OCTOPUS_ACCOUNT, or the only account the API key can see)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4/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 the safety profile is covered. Beyond that, the description adds useful behavior: results are ordered newest first, amounts are in pounds, and a running balance follows each transaction, which tells the agent what the payload conceptually contains. It is silent on the idempotentHint=false annotation and on any pagination or error behavior, keeping it short of 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?

A single front-loaded sentence that opens with the verb and resource before layering on the category list, currency, ordering and balance semantics. Nothing is redundant and no sentence is filler.

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 describing return values and does so reasonably: it names the transaction categories, the currency, the ordering, and that a balance follows each entry. It leaves out pagination mechanics beyond the limit parameter and the meaning of the per-transaction balance (running vs. statement), which is a modest but real gap for a list tool.

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 coverage is 100%, with each of the four parameters documented inline including formats, defaults and the 99 cap, so the baseline is 3. The description reinforces that ordering is newest first (relevant to the limit parameter) and that amounts are in pounds, but adds no date syntax, default-account resolution, or boundary-inclusivity detail beyond what the schema already 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 and resource ('List the account's transactions') and then enumerates exactly what is returned: energy charges, payments such as direct debits, credits such as Octoplus rewards or Saving Session payouts, and refunds, in pounds, newest first. That level of specificity lets an agent distinguish it from siblings like octopus_list_bills or octopus_get_balance without inspecting either schema.

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?

Usage is only implied: the enumeration of transaction categories signals when the tool is appropriate, and the date-range parameters hint at historical lookups. It never states when not to use it or points to alternatives such as octopus_get_balance for a current balance, so the agent must infer routing from sibling names alone.

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