Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CARSXE_API_KEYYesCarsXE API key (required to access the API endpoints). Get one at https://api.carsxe.com/dashboard/developer

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get-vehicle-specsB

Get comprehensive vehicle specifications by VIN

decode-vehicle-plateB

Decode a vehicle's license plate to get VIN and basic vehicle info

international-vin-decoderB

Decode an international VIN and get detailed vehicle info

get-market-valueB

Get the estimated market value for a vehicle by VIN

get-vehicle-historyC

Get a comprehensive vehicle history report by VIN

get-vehicle-imagesB

Get vehicle images by make, model, and optional filters

get-vehicle-recallsB

Get vehicle recall information by VIN

vin-ocrB

Recognize and extract the VIN from a vehicle image URL using OCR

get-year-make-modelB

Get comprehensive vehicle info by year, make, model, and optional trim

decode-obd-codeB

Decode an OBD code and get diagnosis information

recognize-plate-imageB

Recognize and extract license plate(s) from a vehicle image URL

get-lien-theftA

Get lien and theft information for a vehicle by VIN

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 12 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: OBD decoding, plate decoding, VIN-based lookups (lien, market value, history, recalls, specs), image retrieval by make/model, and OCR for plates and VINs. No two tools overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent hyphenated verb_noun pattern (e.g., decode-obd-code, get-vehicle-history). The naming is predictable and clearly indicates the action and resource.

Tool Count5/5

With 12 tools, the set is well-scoped for a vehicle information server. Each tool addresses a specific need without being excessive or insufficient.

Completeness5/5

The tool set covers major vehicle data categories: VIN decoding, plate decoding, OBD codes, history, market value, theft/lien, recalls, specs, images, and OCR. No obvious gaps exist for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues