Skip to main content
Glama

cOBD

Fault codes

get_fault_codes
Read-onlyIdempotent

The fault codes one car reported, whether each is still active, and what it means.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
carYes
codesYes
unitsYes
statusYes
headlineYes
disclaimerYes

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and a closed-world scope, so the safety profile is fully covered. The description adds only that results include active-status and meaning fields, which the output schema already conveys. No additional context on ordering, volume, or clearing history is provided.

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 short sentence with no filler, and the resource plus scope are front-loaded. It is a sentence fragment rather than a complete statement, which slightly weakens clarity about the action being performed.

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?

The tool is simple, with one optional parameter, an output schema, and rich annotations, so most burden is already carried by structured data. However, given three fault-code-related siblings, the description does not do enough to prevent an agent from selecting the wrong one.

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 car_id property already documents the default ('Without it, the car driven last'). The description's 'one car' phrasing is consistent with the single-car scope but adds no syntax, format, or edge-case detail beyond the schema.

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 (fault codes) with a clear scope (one car) and states the payload fields: active status and meaning. It is more than a restatement of the name, but it offers no differentiation from siblings like search_fault_codes or explain_fault_code, whose names suggest overlapping territory.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'one car reported' only weakly implies this is the per-car lookup versus a cross-car search, and nothing addresses whether to call explain_fault_code instead for interpretation, even though 'what it means' overlaps with that sibling's apparent purpose.

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