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

connected-vehicle-health

by imsnawaz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Clear DTCs (action)

clear_dtcs
Destructive

Clears stored and pending diagnostic trouble codes and resets the malfunction indicator light. Confirmation required to execute.

Instructions

Clear stored and pending DTCs and reset the MIL. Requires confirm=true. Disabled for read-only backends (e.g. Salesforce).

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": {
      "vin": "<vin>"
    },
    "name": "clear_dtcs"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYesVehicle VIN
confirmNoMust be true to execute this write action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and openWorldHint=true. The description adds specificity: it resets the MIL, requires confirm=true, and is disabled for read-only backends. No contradiction with annotations.

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?

Two sentences, front-loaded with the main action, then critical usage conditions. No wasted words.

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 action tool with established annotations and no output schema, the description covers the core behavior, conditions, and limitations. It lacks details on return value (e.g., success indication) but is sufficiently complete.

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%, so the schema fully documents both parameters. The description only reiterates the confirm requirement, adding minimal extra meaning. Baseline 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 states a specific verb and resource: 'Clear stored and pending DTCs and reset the MIL.' This clearly distinguishes it from sibling tools like get_dtcs (retrieval) and decode_dtc (decoding).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description specifies when to use ('clear DTCs'), a prerequisite ('confirm=true'), and when not to use ('disabled for read-only backends'). It does not explicitly compare to siblings but provides sufficient context for 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