Skip to main content
Glama

Battery Payback

UK rules for home batteries

get_rules
Read-only

Quoted official facts on VAT, SEG, MCS, planning, network (DNO) notification, typical costs, solar yield, self-consumption and the Boiler Upgrade Scheme.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
topicNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful trait beyond that — the facts are 'quoted' and 'official', signalling provenance/authority rather than derived or computed values. It omits other relevant behavior: whether facts are versioned or dated (important for regulations), and what is returned when no topic is supplied.

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?

A single compact sentence with no filler, and the subject matter is enumerated up front. It opens with a noun phrase rather than a verb, so the action is slightly less front-loaded than it could be, but nothing in the sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup with one optional enum parameter this is close to adequate, but with no output schema the description should indicate the return shape beyond 'quoted facts' (e.g. verbatim passages, structured records) and clarify behavior when the topic is omitted. The topic coverage is good; the return and default behaviors are not.

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 0%, so the description must carry the parameter burden, and it largely does: every enumerated topic in the schema (vat, seg, mcs, planning, grid-notification, install-cost, solar-yield, self-consumption, boiler-upgrade-scheme) is glossed in prose. What is missing is whether the single topic parameter is optional and what a no-argument call yields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource concretely: quoted official facts, and enumerates the exact subject areas (VAT, SEG, MCS, planning, DNO notification, costs, yield, self-consumption, BES). That is far more specific than the name alone. It does not, however, distinguish this reference-lookup from siblings like get_tariff_facts or get_methodology, which plausibly cover overlapping ground.

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: an agent can infer this is the tool for regulatory/scheme facts, but there is no explicit statement of when to prefer it over get_tariff_facts or get_methodology, and no exclusion of cases where calculate_payback would be the right call. The topic list gives a weak signal but no routing guidance.

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