Skip to main content
Glama
Sign In
oegb-kraken-mcp

oegb-kraken-mcp

by marcospaegle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get account details

get_account
Read-onlyIdempotent

Retrieve Octopus Energy account details by account number to access property meter points, MPAN/MPRN serials, and tariff agreements for consumption and rate lookups.

Instructions

Get an Octopus Energy account by account number (e.g. A-1234ABCD). Needs OCTOPUS_API_KEY. Returns properties with electricity meter points (MPAN, meter serial numbers) and gas meter points (MPRN, serials), plus tariff agreements (tariff_code, valid_from/valid_to). Use these with get_consumption and get_tariff_rates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_number": "<account_number>"
    },
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds two genuinely useful facts not in annotations: an OCTOPUS_API_KEY is required, and the response nests electricity/gas meter points and tariff agreements. It does not mention error behavior for an invalid or unknown account number, which matters for an open-world lookup.

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?

Three sentences ordered as action, auth prerequisite, return shape, then chaining advice. No redundant restatement of the name or title, and every sentence contributes information the agent needs.

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 spends words on the return payload structure and the auth requirement, which is what an agent needs to decide and to consume the result. Only failure modes (invalid account number, not found) are unaddressed, a minor gap for a read-only lookup.

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 description coverage is 0% — the account_number property carries only minLength — so the description must supply meaning, and it does by giving a concrete example format (A-1234ABCD) that tells the agent what shape of value to pass. A single-parameter tool keeps the remaining burden small.

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 (get an Octopus Energy account) plus the exact identifier format (e.g. A-1234ABCD). It also enumerates the payload (MPANs, MPRNs, serials, tariff_code, valid_from/valid_to), which makes it unmistakably distinct from the consumption and tariff-rate siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It positions itself as the entry point by telling the agent to feed the returned meter points and tariff agreements into get_consumption and get_tariff_rates. That is clear workflow context, but there is no explicit exclusion such as when to skip this tool or what to do if the account number is unknown.

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

Deploy Server

Other Tools