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

oegb-kraken-mcp

by marcospaegle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get product details

get_product
Read-onlyIdempotent

Retrieve a product and its regional tariff codes by product code to look up rates with get_tariff_rates.

Instructions

Get one product and its tariffs by product code (e.g. AGILE-FLEX-22-11-25). Public. The response lists tariff codes per region (single_register_electricity_tariffs, dual_register_electricity_tariffs, single_register_gas_tariffs), keyed by GSP region like _A ... _P. Use those tariff codes with 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": {
      "product_code": "<product_code>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_codeYes
tariffs_active_atNoShow the tariffs active at this datetime instead of now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the description's added value is the 'Public' (no auth) note and the disclosure of the return structure — tariff code groups keyed by GSP region _A through _P. It does not cover error behavior for unknown product codes, but it meaningfully extends beyond the annotation block.

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 short sentences, front-loaded with the action and key, then access scope, then response shape and next step. No sentence is redundant or restates the schema.

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 carries the burden of describing the return value and does so concretely — enumerating the three tariff groups and the GSP region keying. Combined with the follow-up tool pointer, an agent has everything needed to call and use the result.

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 coverage is only 50%: product_code has no description at all, and the description compensates by showing its expected format via an example. tariffs_active_at is already fully documented in the schema, so no credit is needed there.

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 one product and its tariffs') plus the keying parameter ('by product code') and a concrete example value (AGILE-FLEX-22-11-25). The singular 'one product' implicitly separates it from the list_products sibling, and 'Public' adds access scope.

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?

Gives explicit downstream routing: 'Use those tariff codes with get_tariff_rates', which tells the agent how this tool chains into the next step. There is no explicit when-not guidance or direct comparison to list_products, so it stops short of a 5.

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