Skip to main content
Glama

Get vehicle details

get_vehicle_details
Read-onlyIdempotent

Restituisce la scheda completa di UN singolo veicolo usato del network DealerMAX (REWIND/NOS). È il drill-down dopo un hit di search_vehicles.

QUANDO usarlo: dopo search_vehicles, per avere TUTTO su una sola auto già individuata.
QUANDO NON usarlo: per cercare/sfogliare il parco usato → search_vehicles; per il
dettaglio di un'offerta NLT → get_nlt_offer_details; per le specifiche tecniche di un
modello a catalogo a prescindere dalla disponibilità → get_vehicle_specs.

Ritorna un oggetto: id_auto; title; description_short/medium/long + seo_description;
specs{} (marca, modello, allestimento, anno_immatricolazione, mese_immatricolazione,
km_certificati, colore, fuel_type, transmission, drivetrain, kw, hp, cilindrata,
classe_emissioni, co2_g_km, consumo_medio, porte, posti); price{} (prezzo_vendita_eur,
currency='EUR', prezzo_netto_iva: true=IVA esclusa/false=IVA inclusa, iva_esposta);
media{} (cover_url, total_media, images[]); highlights[]; faq[];
availability{} (is_attiva, visibile, venduto_il, opzionato_il, last_modified); dealer{}
(name, ragione_sociale, address, cap, city, province, phone, email, latitude, longitude,
google_maps_url, website); podcast e video se presenti; canonical_url e schema_org_url.
Client con immagini inline: embedda cover_url/images; altrimenti link 'Foto veicolo'.
Non trovato → {error, id_auto}.

Read-only, keyless. Rate limit 60 richieste/min per IP.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vehicle_slug": "<vehicle_slug>"
    },
    "name": "get_vehicle_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
vehicle_slugYesIdentificatore di UN veicolo usato. Accetta UUID puro (id_auto) o slug 'marca-modello-id_auto' (l'ultimo segmento UUID viene estratto). Lo prendi dal campo id_auto di un hit di search_vehicles.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / vehicle_slug / description
      Previous value: -"Vehicle identifier. Accepts a pure UUID (id_auto) or a friendly slug like 'marca-modello-id_auto' (the trailing UUID segment is extracted)."New value: +"Identificatore di UN veicolo usato. Accetta UUID puro (id_auto) o slug 'marca-modello-id_auto' (l'ultimo segmento UUID viene estratto). Lo prendi dal campo id_auto di un hit di search_vehicles."
  2. Changed1 schema field changed
    • addedInput schema / properties / vehicle_slug / description
      Added value: +"Vehicle identifier. Accepts a pure UUID (id_auto) or a friendly slug like 'marca-modello-id_auto' (the trailing UUID segment is extracted)."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive/openWorld), the description adds auth requirements ('keyless'), an explicit rate limit ('60 richieste/min per IP'), the not-found response shape ({error, id_auto}), and client-side image-embedding guidance. These are exactly the behavioral traits annotations cannot express.

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?

Well front-loaded and cleanly sectioned (purpose → when/when-not → return shape → behavior). It loses a point because the long enumeration of every returned field is verbose and largely redundant with the existing output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with a full output schema and covering annotations, the description supplies everything an agent needs: routing, error behavior, rate limits, and return handling. Nothing material is missing.

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% and the schema already documents that vehicle_slug accepts a bare UUID or a 'marca-modello-id_auto' slug with last-segment extraction. The description restates this without adding syntax or format detail 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('scheda completa di UN singolo veicolo usato del network DealerMAX') and explicitly positions itself as the drill-down after search_vehicles. An agent can distinguish it from every sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'QUANDO usarlo' and 'QUANDO NON usarlo' sections name the alternatives (search_vehicles for browsing, get_nlt_offer_details for NLT offers, get_vehicle_specs for catalog specs) and the condition that selects each. Nothing is left to inference.

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