Skip to main content
Glama

cOBD

Drive score

get_drive_score
Read-onlyIdempotent

How smoothly one car was driven, from hard braking, acceleration and cornering. Pro plan.

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

Input Schema

NameRequiredDescriptionDefault
daysNoDays of driving to score, 1 to 365. Default 30.
car_idNoA car id from list_cars. Without it, the car driven last.

Output Schema

NameRequiredDescriptionDefault
carNo
daysNo
gradeNo
scoreNo
unitsYes
breakdownNo
upgrade_urlNo
pro_requiredNo

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 closed-world scope, so the safety profile is covered. The description adds genuine context beyond that: the score is computed from hard braking, acceleration, and cornering events, and access requires a Pro plan. It does not say what happens when the plan requirement is unmet (error vs. unavailable field), which is the main behavioral gap.

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?

Two short sentences, front-loaded with what the score measures, followed by the plan constraint. 'Pro plan.' is a fragment but carries real information; nothing is padded, though the description is arguably too terse for a tool with an implicit verb.

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?

Parameter semantics are fully covered by the schema and return values are covered by the output schema, so the core call contract is intact. For a read-only scoring tool, the missing piece is how it relates to the near-identical get_health_score sibling and what a non-Pro-plan caller should expect.

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 schema itself documents the days range and default plus the car_id fallback semantics ('Without it, the car driven last') with a pointer to list_cars. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 (a per-car drive score) and enumerates its inputs (hard braking, acceleration, cornering), so an agent knows what it returns. It does not differentiate itself from the sibling get_health_score, which reads as a similar scoring tool, leaving the agent to infer the distinction.

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 statement of when to use this versus get_health_score, get_car_status, or list_drives, and no exclusions. The only usage-adjacent information is the 'Pro plan' prerequisite, which tells the agent about access gating but not tool selection.

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