Skip to main content
Glama

cOBD

Car status

get_car_status
Read-onlyIdempotent

The latest readings from one car, such as engine speed, coolant, fuel level and battery, and its check-engine state.

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

Input Schema

NameRequiredDescriptionDefault
car_idNoA car id from list_cars. Without it, the car driven last.

Output Schema

NameRequiredDescriptionDefault
carYes
timeYes
unitsYes
readingsYes
fault_lampYes
age_minutesYes

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes the notion of freshness ('latest readings') and the check-engine state, but says nothing about staleness windows, units, or whether readings can be null when the car is offline. Additional context is modest given the annotations already carry the operation semantics.

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 front-loaded sentence with no filler; the field examples are the useful payload. It is a noun phrase rather than a verb-led statement, which slightly weakens the framing but costs no length.

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?

An output schema exists, so return values need no prose explanation, and the single optional parameter is fully documented in the schema. What remains missing is routing against the metric-specific siblings, which matters in this crowded catalog but is not fatal for a one-parameter read.

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%, and the schema itself documents the fallback ('Without it, the car driven last') plus the id source (list_cars). The description adds nothing about how car_id affects the response or what happens with an unknown id, so the baseline of 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 (the latest readings from one car) and enumerates representative fields (engine speed, coolant, fuel level, battery, check-engine state), so an agent knows exactly what comes back. It does not distinguish this general snapshot from narrower siblings such as get_fuel or get_fault_codes, keeping it out of the 5 band.

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: the breadth of covered readings suggests a general 'give me everything currently' call, and the optional car_id default (last driven car) hints at the common case. There is no explicit statement of when to prefer this over get_fuel, get_fault_codes, or get_health_score, so the agent must infer routing.

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