Skip to main content
Glama
Sign In
OBD MCP Server

OBD MCP Server

by ayhammouda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get vehicle status

obd_get_vehicle_status
Read-onlyIdempotent

Reads vehicle connection and ECU status to monitor diagnostic readiness. Use this to check if the ECU is communicating properly.

Instructions

Read connection and ECU status. This is an observation, not a roadworthiness determination.

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": {
      "vehicle_id": "<vehicle_id>"
    },
    "name": "obd_get_vehicle_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
vehicle_idYes

Output Schema

NameRequiredDescriptionDefault
ecusNo
notesNo
vehicleYes
observed_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds that it reads connection and ECU status, clarifying the scope beyond 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, each adding value: first states action, second adds important clarity. No wasted words.

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 the simplicity of the tool and presence of an output schema, the description is somewhat complete, but the lack of parameter semantics is a notable gap.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description does not explain the sole parameter 'vehicle_id' or its purpose/format, leaving the agent without necessary context.

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?

Clearly states it reads connection and ECU status, with a note distinguishing from roadworthiness determination. The verb and resource are specific, but it does not explicitly differentiate from sibling read tools.

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?

Provides context by saying it's an observation, not a roadworthiness check, but no explicit guidance on when to use vs. alternatives like obd_read_standard_pids or obd_read_dtcs.

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