Skip to main content
Glama
Sign In

Octopus Energy

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Grid Supply Point

grid_supply_point
Read-onlyIdempotent

Map a UK postcode to its GSP (Grid Supply Point) group "_A".."_P". The group_id is the region suffix used in tariff codes and in product_details regional breakdowns. Returns {count, results:[{group_id}]}.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postcode": "SW1A1AA"
    },
    "name": "grid_supply_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeYesUK postcode, e.g. "SW1A 1AA" (spaces optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "postcode": "SW1A1AA"
+  }
+]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, open-world, idempotent, and non-destructive. The description adds the output format ({count, results:[{group_id}]}) but does not disclose additional behaviors beyond what annotations imply.

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?

The description is two sentences, front-loads the primary action, and contains no redundant information. Every sentence adds value.

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?

Given the simple one-parameter input and complete annotations, the description adequately covers the purpose, output structure, and real-world significance. It lacks error handling or edge cases but is sufficient for a straightforward mapping 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?

The input schema fully describes the postcode parameter (type, example, spaces optional). The description adds context about the output group_id range but does not enhance parameter understanding 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?

The description clearly states the tool maps a UK postcode to a GSP group, explaining the group_id suffix and its relevance to tariff codes and regional breakdowns. This is specific and distinguishes the tool's core function.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like tariff_unit_rates or product_details. There is no mention of prerequisites or when not to use it.

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

All Octopus Energy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources