Skip to main content
Glama

cOBD

Engine health

get_health_score
Read-onlyIdempotent

One car's engine health score from 0 to 100, part by part. Pro plan.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
carNo
scoreNo
unitsYes
componentsNo
upgrade_urlNo
pro_requiredNo

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?

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and an output schema exists to explain returns. The description adds one genuinely non-structured detail, the 'Pro plan' entitlement constraint, but it does not say what happens when the plan is missing or when a car has no score.

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?

The description is short and front-loads the core output definition. The trailing 'Pro plan.' fragment is terse to the point of ambiguity, but the overall wording contains no filler.

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?

Given rich annotations, an output schema, and a fully documented single optional parameter, the description is adequate but thin. It omits routing guidance against closely related score and fault tools and does not clarify what 'part by part' returns or how entitlement failures surface.

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 coverage is 100% and the single optional car_id already documents the fallback ('the car driven last'), so the description adds no parameter meaning. The baseline 3 applies because the schema fully carries parameter semantics.

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 (engine health score) with a defined range (0-100) and a structural detail ('part by part'), which distinguishes it reasonably well from siblings like get_drive_score or get_fault_codes. It does not explicitly contrast itself with those siblings, 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 Guidelines2/5

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

There is no when-to-use guidance and no exclusions or alternatives named. The only contextual clue is the 'Pro plan' note, which signals availability rather than when an agent should call this instead of get_drive_score, get_car_status, or get_fault_codes.

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