Skip to main content
Glama

Saving Sessions

octopus_get_saving_sessions
Read-only

Fetch upcoming Octoplus Saving Sessions with times, reward rates, join status and codes, plus your points balance and past session results.

Instructions

Get Octoplus Saving Sessions (and turn-up and weekend happy hour sessions): upcoming sessions for your region with their start and end times, the OctoPoints reward per kWh, whether you've joined each one and the code to join it; whether you've signed up to the campaign; your points balance; and results of past sessions you took part in.

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

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

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds real context beyond that: it scopes results to 'your region', discloses that join codes and join status are included, and separates current campaign state from historical results — which matters given there is no output schema. It stops short of describing pagination, freshness, or what happens when the account is not enrolled.

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?

It is a single front-loaded sentence with the primary resource named first and the enumerated contents following, so nothing is buried. The semicolon-separated clause list is dense and slightly hard to parse, but each clause carries distinct information rather than 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 correctly absorbs the burden of explaining return values and does so thoroughly — session times, reward rate, join state, join code, campaign status, balance, history. What remains thin is the account/region scoping behavior and the lack of any alternative-tool routing, minor for a read-only retrieval 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 description coverage is 100%, so both parameters (limit, account_number) are fully documented in the schema, including the 'newest first' ordering and the environment-variable fallback. The description only indirectly touches them via 'results of past sessions you took part in', which hints at what limit controls. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific resource (Octoplus Saving Sessions, including turn-up and weekend happy hour variants) and enumerates what the tool returns: upcoming sessions with start/end times, OctoPoints per kWh, join status and join code, campaign signup state, points balance, and past session results. That is far more than a restatement of the name. It does not, however, distinguish itself from close siblings like octopus_get_octoplus or octopus_get_balance, so an agent must infer the boundary.

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 rather than stated: an agent can infer this is the tool for saving-session and Octoplus campaign data, and the parenthetical clarifies which session types count. There is no explicit when-to-use versus octopus_get_octoplus or octopus_get_balance, and no mention of prerequisites such as needing to be enrolled in the campaign or having a region set.

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