Autohaus Ehrl

Get FULL details for one vehicle by its numeric id. USE THIS whenever the customer asks what a vehicle has, what is special about it, or about Ausstattung/Extras: search results deliberately omit all of it. SCOPE MATTERS, and the equipment buckets disagree on purpose. `optional`, `paint`, `interior` and `upholstery` describe THIS vehicle. `standardForModelLine` is the model LINE’s catalogue, NOT a statement about this car, and it lists values this car does not have. PRECEDENCE when they conflict: a specific field or an entry in `optional` WINS over `standardForModelLine`. Never quote the catalogue as this vehicle’s configuration, and never present a conflict as two features — if only the catalogue mentions something, say it is the model line’s standard rather than a confirmed property of this car. Features recur across buckets under different wording ("Lenkrad heizbar" / "Lenkradheizung"); exact repeats are removed, near-duplicates are not — do not count them twice. If `equipment.truncated` is true, say "und weitere" rather than implying the list is complete. Quote `technicalData` labels and values as given; do not regroup or convert them. `consumption.status` is ALWAYS present: `available` (quote `consumption.text` with any price, as Pkw-EnVKV requires), `not_required_for_this_vehicle` (no disclosure is owed — say consumption is not stated), or `missing_from_source`. In the latter two, say the figures are unavailable and NEVER estimate them or substitute typical values for the model. `financing` and `leasing` are DIFFERENT products: leasing has a Sonderzahlung and a mileage allowance and NO interest rate; financing has interest rates and a final payment. Do not describe one in the other’s terms. If you name any rate, term, mileage allowance or interest figure you MUST also give that offer’s `disclosure` verbatim — it is the required representative example. Do not compute, round or combine the numbers, do not derive a monthly figure yourself, and do not present an offer as binding; it is subject to credit approval. If a vehicle has no `financing` or no `leasing` key, say that offer type is not published for it rather than quoting the other one. `versionSpecs`/`technicalData` are often ABSENT. If a figure the customer asked for is missing, say it is not available for this car and refer to the dealer. NEVER take one from the web or your own model knowledge: it describes a different build and has been wrong.

vehicle_detail

Show vehicles as a visual card list, a detail view, a side-by-side comparison, or the narrowing OPTIONS for the current stock. Use view="list" after a search the customer wants to browse, view="detail" for one vehicle, view="compare" when they are weighing two to four against each other, and view="options" when the customer has NOT yet said what they want ("was habt ihr", "ich schaue mich nur um", "keine Ahnung, was passt"). view="options" renders NO vehicles on purpose — it shows the customer what can be narrowed down: price range, fuel, gearbox, condition and body style, plus the commercial flags (deductible VAT, quality seal, metallic). Drivetrain, colour, upholstery and emission class are one click away behind "Weitere Filter" — mention them as available, not as displayed. Use it INSTEAD of showing six arbitrary cars out of a large inventory. Do NOT use it when the customer already stated constraints — go straight to view="list". Pass the SAME structured arguments you would pass to vehicle_search — this tool runs the search itself. For detail and compare, pass `ids` from earlier results instead. CALL THIS FIRST for a browse, and AT MOST ONCE per customer request. Each call adds a SEPARATE widget to the conversation — it does not replace the previous one — so an exploratory call followed by a corrected one leaves the customer looking at two lists, the first of which is wrong. You do NOT need to search first to get this right: this tool runs the search itself and returns the total, the applied filters, any notes and the full data for every vehicle — everything vehicle_search would have told you, and it paints at the same time. When the customer has stated what they want, the filters are already settled: render immediately. Use vehicle_search BEFORE rendering only in the two cases where a list must not appear yet: picking a handful of vehicles out of many to pass back as `ids`, or answering a pure count/aggregate question that needs no cards. The list FETCHES up to 24 vehicles and the widget pages over them locally (the customer picks 6, 12 or 24 per page), so you do not need to ask for a page. Use `skip` only to go PAST the block that was fetched ("zeig mir weitere").

render_vehicles

Search this dealer's live vehicle inventory and get the results as TEXT. This tool shows the customer NOTHING. For a browse — any request where the customer will want to see the cars — call render_vehicles instead and call it FIRST: it runs the same search, returns the same totals and data, and paints. Use this tool when a list must not appear yet: to pick a few vehicles out of many for render_vehicles `ids`, or to answer a count/aggregate question. ALWAYS do both of the following in the same call: (1) put the customer's own wording in `query` — the model name is matched from it; and (2) ALSO set an argument for every constraint the customer states, INCLUDING the brand. Numbers and categories MUST be passed as arguments: the server-side text parser mishandles German bounds (it reads "unter 30.000 €" as a *minimum*), cannot see transmission, drivetrain, colour or seat count at all, and guesses wrongly at brands, so a constraint left only in `query` will silently not be applied. Examples — "Kombi mit Automatik unter 30.000 €": query="Kombi mit Automatik unter 30.000 €", bodyType="Kombi", gearbox="Automatik", priceMax=30000. "7-Sitzer Diesel, höchstens 60.000 km": query=…, seatsMin=7, fuel="Diesel", mileageMax=60000. "BMW Kombi": query="BMW Kombi", manufacturer="BMW", bodyType="Kombi". "4-Sitzer": query="4-Sitzer", seatsMin=4, seatsMax=4 — an exact count needs BOTH bounds; seatsMin alone means "at least", which answers a four-seater request with seven-seaters. Use the customer's own words for the category arguments ("Automatik", "Allrad", "rot") — never ids or codes; the server resolves them against this dealer's vocabulary. The reply lists each vehicle with its id, price, specs and the statutory consumption/CO2 disclosure. When you quote a price to the customer, repeat that disclosure line with it — under German Pkw-EnVKV it must appear wherever a price is shown. It also reports which filters were understood; if a constraint is missing from that list, say so rather than implying the results match it. ZERO RESULTS IS A REAL ANSWER. If a search with your arguments returns nothing, tell the customer this dealer has none and offer an alternative you can name from a NEW, deliberately broader search. Do NOT re-run the same request with the arguments removed: a search with no arguments returns the whole inventory, which looks like a list of matches and is not one.

vehicle_search

Financing and leasing products for ONE vehicle: the terms, mileages and deposits each permits, plus the `calculators` this dealer runs. Both are inputs to a quote — call this first and pass its values, never guessed ones. No products means no live calculator is configured — NOT that the vehicle cannot be financed. Never say that; use the representative example from vehicle_detail instead.

vehicle_financing_options

Recalculate the monthly instalment at a chosen term, mileage or deposit — this answers "what about 24 months instead of 12". `product` comes from vehicle_financing_options; it and `term` are both required. The calculator SNAPS values it does not permit: report `applied`, never what you asked for, and say so when `snapped` is true. Quote `disclosure` VERBATIM with any figure — legally required, never paraphrased. If `note` is set there were no figures: relay it, do not invent a rate.

vehicle_financing_quote

Alternatives to a given vehicle, as chosen by the dealer — this is the same list its own website shows under "Diese Fahrzeuge könnten Sie ebenfalls interessieren". Use it when the customer asks for something similar, cheaper, newer, or "was habt ihr noch". Prefer it over running another search for that: the selection is the dealer’s judgement of what substitutes for this car, and a search of your own is not. The vehicle you asked about is excluded. The count is whatever the dealer considers genuinely comparable and is often small — do NOT tell the customer that is all the stock there is, and do not describe an empty result as the vehicle being unique. Each entry carries the statutory consumption/CO2 disclosure; repeat it whenever you quote one of these prices.

vehicle_similar