Skip to main content
Glama
Sign In
connected-vehicle-health

connected-vehicle-health

by imsnawaz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Decode DTC

decode_dtc

Decode diagnostic trouble codes to identify the affected system, common causes, symptoms, and recommended repair steps.

Instructions

Explain a diagnostic trouble code: system, likely causes, symptoms, and recommended actions.

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": {
      "code": "<code>"
    },
    "name": "decode_dtc"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesDTC code, e.g. 'P0420'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'explain' without indicating that it is read-only, whether it requires network access, or how it handles invalid codes. More transparency is needed.

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, well-structured sentence that conveys the essential information without any extraneous words. It is front-loaded and efficient.

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 tool with one parameter and no output schema, the description adequately explains the output structure (system, causes, symptoms, actions). It lacks details on edge cases or prerequisites but is reasonably complete given the low complexity.

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% with a single parameter 'code' described as 'DTC code, e.g. 'P0420''. The tool description does not add additional semantic value beyond that, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'explain' and the resource 'diagnostic trouble code', and specifies the content of the explanation (system, causes, symptoms, actions). This distinguishes it from sibling tools like 'clear_dtcs' and 'get_dtcs'.

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?

The description does not provide any guidance on when to use this tool versus its siblings. It lacks explicit context on prerequisites, when-not-to-use, or alternatives, leaving the agent to infer usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools