Skip to main content
Glama

CarsXE (Unofficial)

Carsxe History

carsxe_history
Read-onlyIdempotent

Title/history records for a VIN, title history, brand records (salvage/flood/etc.), odometer readings and junk/insurance records. Example: carsxe_history({ vin: "WBAFR7C57CC811956", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vin": "WBAFR7C57CC811956",
      "_apiKey": "your-carsxe-api-key"
    },
    "name": "carsxe_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYes17-character Vehicle Identification Number
_apiKeyYesYour CarsXE API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that: no note on data coverage (e.g., region), whether records can come back empty, cost/quota, or latency for an external API call.

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?

A single front-loaded sentence listing what is returned, followed by a call example. Nothing is padded, though the example largely duplicates the schema's own examples field and so earns less than a full-marks placement.

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?

With no output schema, the description is the only place the return shape could be described, and it only lists category names without saying how records are structured, whether fields can be null, or how to read a 'no records found' result. For a read-only lookup with fully documented inputs, that is adequate but leaves a real gap.

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%, so both parameters (17-character VIN, API key) are already fully documented. The inline example restates the same input without adding meaning such as VIN normalization behavior or what happens with an invalid VIN.

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 and enumerates the concrete record types it returns (title history, brand/salvage/flood records, odometer readings, junk/insurance records). That makes the purpose unmistakable. It does not, however, distinguish itself from siblings like carsxe_vin_specs or carsxe_market_value, leaving the agent to infer the boundary.

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?

There is no explicit when-to-use/when-not-to-use guidance and no named alternative. Usage is only implied by the enumerated record types, which suggest a vehicle-history/accident/salvage check rather than a specs or valuation lookup.

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.