Skip to main content
Glama

Battery Payback

How Battery Payback calculates

get_methodology
Read-only

The calculator model, its simplifications, sourced defaults and how to cite the site.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description does not need to restate it. What the description does add is content-level disclosure: that the material includes acknowledged simplifications and sourced defaults, plus citation instructions, which is meaningful context for an agent that might otherwise treat the output as authoritative calculation logic. It stops short of saying whether the result is static prose, a document link, or structured data.

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 short line with no filler, and the most decision-relevant items (the model and its simplifications) come first. It is a sentence fragment rather than a complete clause, which slightly hurts readability but not economy.

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, zero-argument read tool with annotations covering safety, the description is close to sufficient because it names the topics returned. Since there is no output schema, it should still say what form the answer takes (prose, links, structured document) and ideally flag that this is reference material rather than computed output.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The input schema confirms an empty object with additionalProperties false, consistent with a no-argument reference endpoint.

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

Purpose3/5

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

The description enumerates the content of the resource (calculator model, simplifications, sourced defaults, citation guidance), which tells an agent roughly what this returns. But it is a bare noun phrase with no verb, so it never explicitly says 'returns the methodology documentation.' It also does not distinguish itself from sibling get_rules or get_tariff_facts, which plausibly overlap in subject matter.

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 when-to-use guidance at all. With siblings like get_rules and get_tariff_facts in the same domain, an agent has no statement of which tool answers which question or when this explainer should be preferred over those data tools.

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