Skip to main content
Glama

Octoplus status and points

octopus_get_octoplus
Read-only

Check if an Octopus Energy account is enrolled in Octoplus and retrieve its OctoPoints balance with the pound value Octopus assigns.

Instructions

Get whether the account is enrolled in Octoplus, Octopus's rewards scheme, and its OctoPoints balance with the value Octopus gives it in pounds.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many past sessions you took part in to include, newest first (default 5)
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. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "How many past sessions you took part in to include, newest first (default 5)",
      +  "type": "integer"
      +}
    • removedInput schema / properties / past_limit
      Removed value: -{
      -  "description": "How many past sessions you took part in to include, newest first (default 5)",
      -  "type": "integer"
      -}
  2. First observedv0.4.1

TDQS

B3.4/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 safety is covered. The description adds only definitional context (Octoplus is a rewards scheme, points are valued in pounds) and says nothing about what the `limit`-driven session lookup returns or why users appear in the response. The idempotentHint=false flag on a read-only get is also left unexplained.

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?

A single front-loaded sentence with the resource first and the defining gloss about the rewards scheme second. The trailing phrase 'with the value Octopus gives it in pounds' is slightly awkward but carries real meaning and is not padding.

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?

There is no output schema, so the description must carry the return contract; it names enrollment status, point balance and pound value, which is a reasonable start. However, the presence of a `limit` parameter for past sessions implies the response also includes session history, which the description never mentions, leaving the actual shape partly unexplained.

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 both `limit` and `account_number` are documented in the schema and the baseline of 3 applies. The description adds no parameter meaning at all and never mentions the past-sessions dimension that `limit` controls, so it does not compensate for the conceptual gap between the parameter and the stated purpose.

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: retrieve Octoplus enrollment status plus the OctoPoints balance and its pound valuation. It also defines what Octoplus is (a rewards scheme), which separates it from the sibling octopus_get_balance. It stops short of naming any alternative, so it stays at 4.

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: an agent can infer this is the tool for rewards/points questions, but there is no explicit when-to-use, when-not-to-use, or routing against siblings such as octopus_get_balance or octopus_list_transactions. Nothing is misleading, but nothing guides selection either.

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