Skip to main content
Glama

cOBD

Car location

get_car_location
Read-onlyIdempotent

Where one car was last, with a map link. The driver allows this separately.

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

Input Schema

NameRequiredDescriptionDefault
car_idNoA car id from list_cars. Without it, the car driven last.

Output Schema

NameRequiredDescriptionDefault
carYes
latYes
lonYes
timeYes
unitsYes
map_urlYes
speed_kphYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a safe, read-only, idempotent, closed-world call, so the bar is lower. The description still adds real context the annotations cannot: the result is a past (last known) position rather than a live one, it includes a map link, and access is gated by a separate driver permission — useful for anticipating empty or denied results.

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 the capability and followed by the constraint; no wasted wording. The second sentence is slightly cryptic ('allows this separately' without naming a consent setting), which costs a point but not clarity of the whole.

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, so return shape needn't be restated, and the single parameter is fully documented in-schema. Combined with the staleness and consent hints, the description is adequate for a simple read tool; only the consent condition remains underspecified.

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 car_id property already explains 'A car id from list_cars. Without it, the car driven last.' The description's 'one car' only reinforces the single-car scope and adds no format or default information beyond the schema, 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?

Names a specific verb and resource ('where one car was last') plus a distinguishing output trait ('with a map link'), which is enough to separate it from get_car_status, get_fuel, or list_cars. It stops short of explicitly contrasting with any sibling, but the purpose is unambiguous.

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?

'The driver allows this separately' flags a consent/permission prerequisite that conditions use of the tool, and 'was last' signals this is retrospective rather than live. It does not state when to prefer it over a sibling or what happens when consent is absent, so guidance is implied rather than explicit.

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