Skip to main content
Glama

Ampworth

Network connection route

connection_route
Read-onlyIdempotent

Work out which ENA connection procedure a domestic installation of solar panels, batteries or both falls under: connect first and notify the distribution network operator within 28 days, or apply and wait for approval before anything is connected.

The rules are the ENA's engineering recommendations, not MCS documents: EREC G98 for small installations, EREC G99 for everything larger, and EREC G100 for export limitation. Every test is in amps per phase at a nominal 230 V, and it applies to the premises as a whole, so list EVERY inverter that can export, existing ones included. A battery counts as generation even if it only ever charges from the panels.

The figure that counts is each inverter's registered capacity: its AC rating, or a lower limit the manufacturer has fixed. It is NOT the panels' kWp. A 4.4 kWp array on a 3.68 kW inverter is a 3.68 kW installation. Where an inverter has been capped below its hardware rating, give the hardware rating as 'designCapacityKw', because G99 tests that separately.

The routes are: G98 when the total is 16 A per phase or less (3.68 kW single phase, 11.04 kW three phase); G99 SGI-1, also connect and notify, when the total is within 16 A but an inverter built for up to 32 A has been capped; G99 SGI-2 and SGI-3, fast track applications answered within 10 working days, which allow larger totals held back by a type-tested export limiter; and the standard G99 application for anything else. An export limiter NEVER brings an installation under G98.

IMPORTANT: this says which procedure applies, not what the operator will decide. Approval depends on the local network, which only the operator can assess. Say so whenever you report a result.

Method from EREC G98 / G99. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phasesNoThe supply: 1 for single phase, which is almost every British house, or 3 for three phase. Defaults to 1.
devicesYesEvery inverter at the premises that can export: solar, battery and hybrid, existing ones included. A battery counts even if it only charges from the panels. At least one is required.
exportLimitKwNoThe export limit a fully type-tested G100 scheme would hold the premises to, in kW per phase, where one is proposed. Optional. An export limit never brings an installation under G98, but it decides which G99 route applies.
otherInstallationsNearbyNoTrue when the same installer has fitted, or plans to fit, generation at other premises within 500 metres, or on the same street, within 28 days either side. That turns a G98 notification into an application. Defaults to false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesYes
routeYes
methodYes
phasesYesRegistered capacity on each phase, in kW and in amps at the nominal 230 V the recommendations use.
devicesYes
totalKwYesRegistered capacity of every device added together.
verdictYes
warningYesWhich route applies is arithmetic; what the network operator decides is not. Always present.
g98LimitKwYes16 A per phase at 230 V: 3.68 kW on a single phase supply, 11.04 kW on three phase.
referencesYes
worstPhaseAYesCurrent on the most heavily loaded phase. This is the figure the thresholds are tested against.
alternativesNoChanges that would put the installation on an easier route, and what each would cost.
exportLimitANoThe proposed export limit converted to amps per phase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, openWorldHint=false), the description discloses important behavioral limits: it says which procedure applies but not what the operator will decide, and instructs the agent to repeat that caveat whenever reporting a result. It also discloses the underlying method (EREC G98/G99) and that all tests are in amps per phase at 230 V across the whole premises.

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?

Long, but front-loaded with the outcome (which procedure applies) before the rules, and nearly every sentence carries a decision-relevant fact. Minor redundancy: the 'export limiter never brings an installation under G98' point appears in the main prose and again in the schema description.

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?

An output schema exists, so return values need no explanation. For a read-only rule-evaluation calculator the description supplies everything an agent needs to call it correctly: the capacity semantics, the premises-wide scope, the phase handling context, the neighbour-proximity trigger, and the mandatory caveat about operator discretion.

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 100%, so the schema carries the basics. The description still adds real semantic value: registered capacity is the inverter's AC rating, not panel kWp; designCapacityKw matters only for inverters capped below hardware rating because G99 tests it separately; a battery counts as generation even if it only charges from panels; every exporting inverter including existing ones must be listed. It adds meaning beyond the schema for several fields.

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 precise verb and outcome: determining which ENA connection procedure (connect-and-notify vs apply-and-wait) a domestic solar/battery installation falls under. It names the governing documents (EREC G98/G99/G100) and the exact decision rules, so an agent can distinguish it cleanly from the solar_pv_* sizing and output calculators.

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?

The description explains the domain logic thoroughly and frames the tool as a method-following calculator 'for understanding a system and checking a quotation', which implies when it applies. However, it never names a sibling tool or states when another calculator should be used instead, and gives no explicit exclusions, so usage is implied rather than stated.

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