Skip to main content
Glama

BRAINIAC Official Property & Energy Lookups

Look up the Ofgem default tariff cap

property-official_ofgem-price-cap-lookup
Read-onlyIdempotent

Return the Ofgem GB domestic energy price cap for a region, fuel, meter and payment method for the vendored charge restriction period before you buy, let, or market a property. Call with region and fuel; optional meter, paymentMethod, date, annualKwh. Returns period, region, fuel, meter, paymentMethod, exVat, vatRate, and incVat (period includes name, from, to). HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: before you buy, let, or market a property, region, fuel, meter, paymentMethod, date, annualKwh, period, exVat, vatRate, incVat, Look up the Ofgem default tariff cap, ofgem price cap lookup.

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": {
      "region": "<region>",
      "fuel": "<fuel>"
    },
    "name": "property-official_ofgem-price-cap-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNodate, string, date. Optional.
fuelYesfuel, string, one of electricity, gas. Required.
meterNometer, string, one of single-rate, multi-register. Optional.
regionYesregion, string, length 2 to 80. Required.
annualKwhNoannualKwh, number, from 0 to 100000. Optional.
paymentMethodNopaymentMethod, string, one of direct-debit, standard-credit, prepayment. Required.direct-debit

Output Schema

NameRequiredDescriptionDefault
fuelNofuel. String.
exVatNoexVat. Object.
meterNometer. String.
incVatNoincVat. Object.
periodNoperiod. Object.
regionNoregion. String.
sourcesNosources. Array.
vatRateNovatRate. Number.
limitationsNolimitations. Array.
paymentMethodNopaymentMethod. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the added value here is the billing contract: HTTP 200 with status complete, partial, or failed is charged at full price while 4xx/5xx are not. That is genuinely decision-relevant behavior an agent cannot get from structured fields, though auth or rate-limit context is absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core is well front-loaded and efficient, but the trailing 'Keywords:' block re-lists the title, every parameter name, and every return field, which is redundant padding. Roughly a third of the text is repetition rather than information.

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 enumerating return fields is optional, yet the description still names them and adds the important constraint that only the 'vendored charge restriction period' is covered. For a six-parameter, read-only lookup this is nearly complete; only guidance on sibling choice is missing.

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?

Schema coverage is 100%, so every parameter is already documented with types, enums, defaults and ranges. The description only restates which params are required vs optional, adding no new semantics such as region naming conventions or how date affects the returned cap period.

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 opens with a specific verb and resource ('Return the Ofgem GB domestic energy price cap') and scopes it by region, fuel, meter, payment method and period. It is instantly distinguishable from the sibling lookups (radon zone, HUD FMR, UK HPI) because the resource and jurisdiction are named explicitly.

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?

It gives clear usage context ('before you buy, let, or market a property') and states mandatory vs optional invocation ('Call with region and fuel; optional meter, paymentMethod, date, annualKwh'). What it lacks is any explicit when-not or reference to a sibling alternative for related property data needs.

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