Skip to main content
Glama

cOBD

List drives

list_drives
Read-onlyIdempotent

One car's drives, newest first, with distance, time, speed, fuel used and weather.

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": "list_drives"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoDrives up to the end of this day, or up to an ISO time with Z or an offset
fromNoDrives from this day, such as 2026-03-01, or an ISO time with Z or an offset
limitNoHow many to return, 1 to 50. Default 10.
car_idNoA car id from list_cars. Without it, the car driven last.

Output Schema

NameRequiredDescriptionDefault
carYes
unitsYes
drivesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 openWorldHint=false, so the safety profile is fully covered. The description adds the result ordering ('newest first') and the fields returned, which is useful context but mostly duplicates what the output schema already carries. It says nothing about pagination behavior, default car fallback, or volume of results.

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?

A single front-loaded sentence with no filler: scope and ordering come first, then the returned fields. Every clause carries information an agent can act on.

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?

An output schema exists and annotations cover safety, so the description needn't explain return values, and it still summarizes them. The one gap is behavior when car_id is omitted and how date-range boundaries interact with 'newest first', both of which live only in the schema.

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 description coverage is 100%, including the date-range semantics of from/to, the 1-50 limit range, and the 'car driven last' default for car_id. The description only echoes the per-car scoping already present in the schema, adding no new parameter meaning. Baseline 3 applies when the schema does the heavy lifting.

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 the resource (drives), the scope (one car), the ordering (newest first), and the payload fields (distance, time, speed, fuel used, weather). That is enough for an agent to distinguish a drive-history listing from siblings like get_drive_score or get_fuel, though it never names an alternative explicitly.

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 explicit when-to-use or when-not-to-use guidance, and no mention of how this differs from summary siblings such as get_drive_score or get_fuel. The only implicit signal is 'one car's drives', which hints at per-car scoping but leaves the agent to infer the rest.

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