Skip to main content
Glama

Battery warranty by model year

battery_warranty
Read-onlyIdempotent

The manufacturer's high-voltage battery warranty for a make, model and model year, as the Census EV warranty checker gives it: the term in years and miles (with the trims each term covers where the terms differ by trim), whether it is still in force at an odometer reading where that can be established, the battery capacity the warranty guarantees, and whether coverage transfers to a later owner. A term is marked estimated when it is not the manufacturer's own figure. Returns established: false and no term when the versions of that model year disagree or have not been researched. Includes the model's battery-warranty fact sheet on censusev.com where one exists.

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": {
      "make": "<make>",
      "model": "<model>",
      "year": "<year>"
    },
    "name": "battery_warranty"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesMake, e.g. "Kia". Case, spacing and common short forms ("Chevy", "VW") are accepted.
yearYesModel year, e.g. 2023.
modelYesModel, e.g. "EV6". Punctuation and spacing are ignored.
mileageNoOdometer reading in miles. With it, status says whether the warranty is in force where that can be established.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the safe-read profile (readOnly, idempotent, non-destructive); the description goes well beyond by disclosing the return payload, how estimated figures are flagged, and the exact failure mode (established: false, no term) when data is conflicting or unresearched. It also notes that a fact-sheet link is included where one exists.

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 opening sentence is a long colon-delimited list that is dense and hard to parse on first read, and the phrasing ('as the Census EV warranty checker gives it') adds atmosphere rather than actionable detail. It is front-loaded with the right information, but the sentence structure could be tightened into discrete clauses without losing content.

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

Completeness5/5

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

There is no output schema, so the description carries the full burden of explaining return values, and it does so thoroughly: term units, trim variation, estimated flags, in-force determination, capacity guarantee, transferability, and the no-data case. For a 4-parameter read-only lookup this leaves nothing an agent needs missing.

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 already 100%, so the baseline is 3. The description adds meaning the schema does not: the mileage parameter is explained as the input that lets status report whether the warranty is still in force 'where that can be established', which clarifies its optional, conditional role.

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?

States a precise verb+resource: the manufacturer's high-voltage battery warranty for a given make/model/year, and enumerates the specific facts returned (term in years and miles, trim coverage, in-force status, guaranteed capacity, transferability). That is clearly distinguishable from the sibling tools, which are all listing/market oriented.

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?

The scope is unambiguous: supply make, model and model year, optionally an odometer reading, to get warranty terms. The description also implies the fallback path (returns established: false when model-year versions disagree or are unresearched). It does not name any alternative tool or state exclusions, so it stops short of a 5.

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