Skip to main content
Glama

Check grid connection headroom

check_grid_connection
Read-only

Check nearest UK electricity Distribution Network Operator (DNO) grid connection headroom for a location: generation/demand headroom (MW/MVA), RAG status, voltage, and a combined BNG+grid siting signal. Covers all of Great Britain (England/Scotland/Wales), not just England. Free, no key.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "check_grid_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so the description is not carrying the safety burden. It nevertheless adds real context beyond the annotations: coverage of all of Great Britain rather than England alone, and that the call is free with no API key required, which matters for auth planning. It does not mention rate limits or latency, keeping it short of a 5.

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?

Front-loaded with the core action and return payload, then scope and cost caveats. Dense but every clause carries information; the '(England/Scotland/Wales)' parenthetical is useful disambiguation rather than padding.

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?

An output schema exists, so return values need not be re-explained, and the description still previews the key fields. The main remaining gap is the undefined coordinate semantics for the two required parameters, which leaves the definition slightly short for a tool whose entire input is positional.

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?

Both parameters are undocumented in the schema (0% description coverage). The description only implies they designate a location, without stating coordinate reference system, acceptable ranges, or precision. Because lat/lon are conventional and self-explanatory names, this is adequate but leaves genuine gaps for anything outside WGS84 degrees.

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?

Names a specific verb and resource ('Check ... DNO grid connection headroom') and states exactly what comes back: generation/demand headroom in MW/MVA, RAG status, voltage, and a combined BNG+grid siting signal. The geographic scope clause separates it from England-only siblings and from the BNG cost/income tools.

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 by 'for a location' and by the mention of a 'combined BNG+grid siting signal', which hints at pairing with the BNG siblings, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent can infer the trigger condition (site screening) but must guess at the boundaries.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources