Skip to main content
Glama

AI ELM

Find fault codes

search_dtc
Read-only

Finds fault codes by part, fault or code prefix (e.g. "oxygen sensor", "misfire", "P04"), in the given language.

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": {
      "query": "<query>"
    },
    "name": "search_dtc"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWords to look for in the code or its name
languageNoLanguage of the texts, ISO 639-1 (default en)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, closed-world lookup, and the description adds useful query-mode context with examples. It does not explain matching semantics such as prefix versus substring behavior, result limits, or what the returned matches contain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence that states the action, searchable field types, examples, and language scope. Every element adds useful information without repetition.

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?

For a simple two-parameter search tool with full schema descriptions and clear read-only annotations, the definition gives enough context to invoke it correctly. The main remaining gap is the absence of result-shape or matching-behavior details, which is notable because there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already high, but the description adds meaning by showing that the query parameter accepts part names, fault descriptions, and code prefixes, with concrete examples like 'oxygen sensor' and 'P04'. It also clarifies that language applies to the texts being searched.

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 states a specific verb and resource: 'Finds fault codes' by part, fault, or code prefix. The examples make the search behavior concrete, but the description does not explicitly distinguish this from the sibling decode_dtc tool.

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?

It implies when to use the tool by describing searchable inputs such as words and code prefixes, including examples. However, it does not state when to use this instead of decode_dtc or any other alternative.

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.