Skip to main content
Glama

cOBD

Fuel

get_fuel
Read-onlyIdempotent

One car's fuel level and range, and its fuel economy over recent days.

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

Input Schema

NameRequiredDescriptionDefault
daysNoDays of driving for the economy, 1 to 365. Default 30.
car_idNoA car id from list_cars. Without it, the car driven last.

Output Schema

NameRequiredDescriptionDefault
carYes
unitsYes
latestYes
economyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is fully covered elsewhere. The description contributes the useful fact that results include both a point-in-time reading (level, range) and a time-aggregated metric (economy over recent days), which tells the agent results mix current and historical data. It says nothing about units, staleness, or behavior when a car has no recent driving 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?

A single tight sentence with the resource and scope front-loaded and no filler. It is a verbless fragment, which costs a little immediate clarity but wastes no words.

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

Completeness4/5

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

The tool is simple, both parameters are fully described, and an output schema exists so return values need not be explained here. What remains missing is minor but real: units for range/economy and what happens for a car with no recent trips.

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 both parameters (days, car_id) are already fully documented, including the default of 30 days and the fallback to the last-driven car. The description only echoes that the economy is computed 'over recent days,' adding no syntax, bounds, or interpretation beyond the schema — 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 a specific resource set — fuel level, range, and fuel economy — scoped to a single car, which clearly separates it from fleet-wide or status-oriented siblings. It lacks an explicit verb and never names a sibling it should be chosen over, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'One car's' signals a per-vehicle read rather than a list, and 'over recent days' hints at the economy window. There is no statement of when to prefer this over get_car_status or get_car_location, and no prerequisites (e.g., needing a car_id from list_cars) are stated in the description even though the schema covers the default.

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