Skip to main content
Glama

Battery Payback

Price cap and smart tariffs

get_tariff_facts
Read-only

Ofgem price cap, smart time-of-use tariffs and export tariffs, quoted with read dates.

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_tariff_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 and the description is not required to restate it. It does add a genuine behavioral detail beyond the annotations — values are 'quoted with read dates', i.e. time-stamped figures — which helps an agent judge data freshness. It says nothing about units, currency, coverage period, or what happens if the topic is omitted.

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?

One compact sentence with the most specific term ('Ofgem price cap') front-loaded and no filler. The fragment form is efficient, though it reads as a list of topics rather than a statement of what the tool does, which slightly blunts clarity.

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?

This is a simple single-parameter read tool with annotations covering safety and no output schema to explain, so the bar is modest and the description is broadly sufficient. The remaining gap is the undocumented default behavior for the optional topic parameter and any hint about the shape of returned figures (units, currency, freshness window).

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 description coverage is 0% and the single 'topic' enum has no per-value documentation, but the description lists the three areas (price cap, smart time-of-use, export tariffs) that map onto the enum values, so it does add some meaning. It does not explain the behavior when the optional parameter is omitted — whether all topics are returned or a default is chosen.

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 a concrete resource set — Ofgem price cap, smart time-of-use tariffs, and export tariffs — plus the annotation that values come with read dates, so an agent knows what content it retrieves. It is a noun phrase without an explicit verb, and it never distinguishes itself from the sibling get_export_rates, which covers an overlapping topic.

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?

There is no statement of when to call this instead of get_export_rates or get_methodology, even though the description explicitly advertises 'export tariffs' that a dedicated sibling appears to handle. No preconditions, no exclusions, no context about regional scope, so the agent must infer routing.

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