Skip to main content
Glama

Car Check

Get fuel economy

get_fuel_economy
Read-onlyIdempotent

Use this when the user asks about mpg, electric range or fuel cost for a car, such as "what mpg does a 2022 Toyota RAV4 hybrid get?". Pass the year, make and model, and optionally words such as AWD or hybrid to narrow it. Returns the EPA's city, highway and combined mpg (mpge for electric vehicles) for each configuration, with electric range, tailpipe CO2 and estimated annual fuel cost, and lists the configurations not shown. EPA estimates, not a promise of real-world mileage.

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

Input Schema

NameRequiredDescriptionDefault
makeYesManufacturer, such as "Honda"
yearYesModel year, such as 2018
modelYesModel name without trim, such as "CR-V"
optionNoOptional words to narrow the configuration, in any order, such as "AWD", "hybrid", "manual" or "4Dr 2.0 L"; every word must match

Output Schema

NameRequiredDescriptionDefault
makeYes
yearYes
modelYes
noticeYes
othersNo
statusYes
messageNo
variantsNo
availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / option / description
      Previous value: -"Optional words to narrow the configuration, such as \"AWD\", \"hybrid\" or \"2.0 L\""New value: +"Optional words to narrow the configuration, in any order, such as \"AWD\", \"hybrid\", \"manual\" or \"4Dr 2.0 L\"; every word must match"
  2. Changed1 schema field changed
    • removedOutput schema / properties / note_from_openkrill
      Removed value: -{
      -  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedOutput schema / properties / note_from_openkrill
      Added value: +{
      +  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are per-configuration, configurations not shown are listed, and the values are EPA estimates rather than real-world guarantees. It does not discuss what happens when the vehicle is unknown or how matching is resolved, which the 'every word must match' option rule makes relevant.

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?

Front-loaded with the usage trigger, then parameters, then return shape, then a caveat — a sensible order with little waste. The sentence about passing year, make and model largely duplicates what the required-fields schema already enforces.

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?

Given a simple four-parameter read tool with full schema coverage, an output schema, and complete annotations, the description supplies everything else needed: when to call it, what comes back, and the estimation caveat. Nothing material 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 description coverage is 100%, so year, make, model and option are already documented, including the 'every word must match' semantics. The description restates the year/make/model requirement and the narrowing role of option without adding format or edge-case detail, so it earns the baseline rather than more.

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?

Specific verb plus resource: it returns EPA city/highway/combined mpg, mpge for EVs, electric range, CO2 and annual fuel cost for a given car. The trigger phrasing ("asks about mpg, electric range or fuel cost") makes it distinguishable at a glance from decode_vin or get_vehicle_report, which address different questions.

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?

Gives a clear when-to-use rule with a concrete example query ("what mpg does a 2022 Toyota RAV4 hybrid get?") and explains how to narrow results with the option field. It does not state exclusions or name an alternative tool for overlapping cases such as a general vehicle report, 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