Skip to main content
Glama

List bills

octopus_list_bills
Read-only

List an Octopus Energy account's bills newest first, including billing period, issue date, charges, credits, and opening/closing balances; optionally include temporary PDF download links.

Instructions

List the account's bills (statements), newest first: the period covered, issue date, charges and credits, and the opening and closing balances, all in pounds. Set include_pdf_links for a temporary link to each bill's PDF.

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

Input Schema

NameRequiredDescriptionDefault
toNoOnly bills issued on or before this date (YYYY-MM-DD)
fromNoOnly bills issued on or after this date (YYYY-MM-DD)
limitNoHow many to return, newest first (default 6, at most 50)
account_numberNoAccount number like A-1234ABCD (default OCTOPUS_ACCOUNT, or the only account the API key can see)
include_pdf_linksNoInclude a temporary download link for each bill's PDF (the link expires after a short time)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.1/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. The description adds real context beyond them: results are ordered newest first, amounts are in pounds, and PDF links are temporary and expire.

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 with the resource and ordering front-loaded and the optional PDF behavior last; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still tells the agent what a bill record contains (period, issue date, charges and credits, opening/closing balances, currency), which is sufficient for a read-only 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%, so all five parameters are already documented, including date formats, the default limit of 6 and cap of 50, and the account_number default. The description only reinforces the newest-first ordering and link expiry, adding little beyond the schema.

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 bills (statements)") and enumerates the returned fields, so an agent can distinguish it from octopus_list_transactions or octopus_get_balance without opening the 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 implied by the description of what bills are and the note to set include_pdf_links when PDFs are wanted, but there is no explicit when-to-use/when-not guidance or named alternative for related data such as transactions or balance.

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