DealerMax

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 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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`vehicle_slug`	Yes	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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, and the description is consistent ('Read-only, keyless'), so no contradiction. Beyond annotations it adds rich context: the full return object shape, the not-found {error, id_auto} case, the 60 req/min rate limit, and client-specific image-handling guidance (embed vs link).

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?

The description is long but logically structured (purpose → when/when-not → return shape → client notes → error case → access limits), front-loading the purpose. The exhaustive return-field listing partially overlaps with the output schema, which costs a point, but the inclusion of conditional fields (podcast/video, client image handling) and routing rules justifies most of the length.

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?

Complete for a single-item read tool: one fully-documented required parameter, full annotation coverage, output schema present, and the description covers routing to alternatives, return shape, not-found behavior, rate limits, and keyless auth. An agent has everything needed to select and invoke this tool correctly.

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% — the schema already explains that vehicle_slug accepts a pure UUID or 'marca-modello-id_auto' slug, that the last UUID segment is extracted, and that it comes from the id_auto field of a search_vehicles hit. The description reinforces the drill-down workflow but adds no new parameter meaning 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+resource: 'Restituisce la scheda completa di UN singolo veicolo usato del network DealerMAX' and positions itself as 'il drill-down dopo un hit di search_vehicles'. The scope (single vehicle detail) is unambiguous and clearly distinguished from siblings in the same sentence.

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?

Has explicit QUANDO usarlo and QUANDO NON usarlo sections naming three alternatives with their exact selection conditions: search_vehicles for browsing the used-car park, get_nlt_offer_details for NLT offer detail, get_vehicle_specs for catalog specs regardless of availability. 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.

All DealerMax tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool maps to a distinct resource and intent: dealer directory, used-car search and detail, NLT search and detail, catalog specs, and market FAQ. The descriptions explicitly cross-reference the other tools and state when not to use them, so misselection is unlikely.

Naming Consistency5/5

All tool names use lowercase snake_case with a clear verb_noun structure: find_* for dealers, search_* for the two inventory searches, and get_* for details and specs. The pattern is predictable and uniform.

Tool Count5/5

Seven tools is well-scoped for a read-only automotive marketplace server: two search/detail pairs for the two offer types, plus dealer lookup, model specs, and market FAQ. No tool feels redundant.

Completeness5/5

The server covers the full discovery lifecycle for its domain: search and drill-down for both used vehicles and NLT offers, dealer lookup, catalog specs independent of inventory, and explanatory FAQ content. Every search entry point has a corresponding detail tool, so there are no dead ends.

Resources

Need Help?