Skip to main content
Glama

Battery Payback

Get one battery

get_battery
Read-only

Specifications from the manufacturer's datasheet and warranty, each with quote and read date.

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": {
      "id": "<id>"
    },
    "name": "get_battery"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYese.g. givenergy-all-in-one (see list_batteries).

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 safety and scope are covered. The description does add genuine value beyond them by disclosing data provenance — that each spec carries a quote and a read date — which signals freshness and traceability, but it says nothing about behavior for unknown IDs or whether fields may be absent.

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 sentence that front-loads the most important information (what data is returned) and wastes no words. It reads as a fragment rather than a complete statement, which slightly reduces clarity but not length efficiency.

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 single-parameter read with annotations and no output schema, the definition covers the data domain and provenance but not the return shape, pagination, or error behavior. It is adequate but leaves the agent to discover the result structure by calling the tool.

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 100%: the single id parameter already has a format pattern, an example (givenergy-all-in-one), and a pointer to list_batteries. The description adds no further parameter meaning, so the baseline 3 applies.

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 specific content resource: manufacturer datasheet specifications plus warranty information, including quotes and read dates. That distinguishes it from calculation siblings like calculate_payback, though the phrasing is a noun fragment with no verb and it never explicitly says it returns a single battery rather than a list.

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 explicit when-to-use statement, no mention of prerequisites, and no named alternative such as list_batteries for discovery or get_tariff_facts for pricing context. Usage is only inferable from the noun phrase describing the returned content.

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