Skip to main content
Glama

haus

by app.onehaus
OverviewDiscussionsAdmin

update_vehicle

Update a vehicle. Only the fields you send change; for text and due-date fields an empty string clears the stored value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVehicle id from list_vehicles.
vinNoVehicle Identification Number, 17 alphanumeric characters.
makeNoManufacturer, e.g. 'Toyota'.
yearNoModel year, 1900-2100.
modelNoModel, e.g. 'Corolla'.
notesNoFree-text notes.
colourNoColour.
motDueDateNoNext MOT (roadworthiness test) due date, YYYY-MM-DD.
taxDueDateNoNext road tax due date, YYYY-MM-DD.
registrationNoRegistration as shown on the plate; format varies by country.
serviceDueDateNoNext service due date, YYYY-MM-DD.
insuranceDocumentIdNoInsurance document id from list_documents.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
titleNo
messageNo
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • changedInput schema / properties / colour / description
      Previous value: -"Colour of the vehicle. Omit to leave unchanged, or send an empty string to clear it."New value: +"Colour."
    • changedInput schema / properties / id / description
      Previous value: -"ID of the vehicle to update."New value: +"Vehicle id from list_vehicles."
    • changedInput schema / properties / insuranceDocumentId / description
      Previous value: -"Document ID of the associated insurance policy document. Omit to leave unchanged, or send an empty string to clear it."New value: +"Insurance document id from list_documents."
    • addedInput schema / properties / insuranceDocumentId / examples
      Added value: +[
+  "01928e4a7d3f7b9ac1e3f6d8b2a4c710"
+]
    • changedInput schema / properties / make / description
      Previous value: -"Manufacturer of the vehicle, e.g. 'Toyota'. Omit to leave unchanged, or send an empty string to clear it."New value: +"Manufacturer, e.g. 'Toyota'."
    • changedInput schema / properties / model / description
      Previous value: -"Model name of the vehicle, e.g. 'Corolla'. Omit to leave unchanged, or send an empty string to clear it."New value: +"Model, e.g. 'Corolla'."
    • changedInput schema / properties / motDueDate / description
      Previous value: -"Date the next MOT (roadworthiness test) is due, in YYYY-MM-DD format. Omit to leave unchanged, or send an empty string to clear it."New value: +"Next MOT (roadworthiness test) due date, YYYY-MM-DD."
    • changedInput schema / properties / notes / description
      Previous value: -"Free-text notes about the vehicle. Omit to leave unchanged, or send an empty string to clear it."New value: +"Free-text notes."
    • addedInput schema / properties / notes / examples
      Added value: +[
+  "Renewed tax disc"
+]
    • changedInput schema / properties / registration / description
      Previous value: -"The vehicle's registration/licence plate as shown on the plate. Free-text; format varies by country. Omit to leave unchanged, or send an empty string to clear it."New value: +"Registration as shown on the plate; format varies by country."
    • changedInput schema / properties / serviceDueDate / description
      Previous value: -"Date the vehicle's next scheduled service is due, in YYYY-MM-DD format. Omit to leave unchanged, or send an empty string to clear it."New value: +"Next service due date, YYYY-MM-DD."
    • changedInput schema / properties / taxDueDate / description
      Previous value: -"Date the vehicle's road tax is next due, in YYYY-MM-DD format. Omit to leave unchanged, or send an empty string to clear it."New value: +"Next road tax due date, YYYY-MM-DD."
    • changedInput schema / properties / vin / description
      Previous value: -"Vehicle Identification Number: a 17-character alphanumeric code unique to the vehicle. Omit to leave unchanged, or send an empty string to clear it."New value: +"Vehicle Identification Number, 17 alphanumeric characters."
    • changedInput schema / properties / year / description
      Previous value: -"Model year of the vehicle. Must be between 1900 and 2100. Omit to leave unchanged."New value: +"Model year, 1900-2100."
  2. Changed23 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "0198c1f4b2c07a1b9e4d5f6a7b8c9d0e",
+    "notes": "Renewed tax disc",
+    "taxDueDate": "2027-09-01"
+  }
+]
    • addedInput schema / properties / colour / description
      Added value: +"Colour of the vehicle. Omit to leave unchanged, or send an empty string to clear it."
    • addedInput schema / properties / colour / examples
      Added value: +[
+  "Blue"
+]
    • addedInput schema / properties / id / description
      Added value: +"ID of the vehicle to update."
    • addedInput schema / properties / id / examples
      Added value: +[
+  "0198c1f4b2c07a1b9e4d5f6a7b8c9d0e"
+]
    • changedInput schema / properties / insuranceDocumentId / description
      Previous value: -"Document ID of insurance policy"New value: +"Document ID of the associated insurance policy document. Omit to leave unchanged, or send an empty string to clear it."
    • addedInput schema / properties / make / description
      Added value: +"Manufacturer of the vehicle, e.g. 'Toyota'. Omit to leave unchanged, or send an empty string to clear it."
    • addedInput schema / properties / make / examples
      Added value: +[
+  "Toyota"
+]
    • addedInput schema / properties / model / description
      Added value: +"Model name of the vehicle, e.g. 'Corolla'. Omit to leave unchanged, or send an empty string to clear it."
    • addedInput schema / properties / model / examples
      Added value: +[
+  "Corolla"
+]
    • changedInput schema / properties / motDueDate / description
      Previous value: -"YYYY-MM-DD format"New value: +"Date the next MOT (roadworthiness test) is due, in YYYY-MM-DD format. Omit to leave unchanged, or send an empty string to clear it."
    • addedInput schema / properties / motDueDate / examples
      Added value: +[
+  "2026-11-15"
+]
    • addedInput schema / properties / notes / description
      Added value: +"Free-text notes about the vehicle. Omit to leave unchanged, or send an empty string to clear it."
    • addedInput schema / properties / registration / description
      Added value: +"The vehicle's registration/licence plate as shown on the plate. Free-text; format varies by country. Omit to leave unchanged, or send an empty string to clear it."
    • addedInput schema / properties / registration / examples
      Added value: +[
+  "AB21 CDE"
+]
    • changedInput schema / properties / serviceDueDate / description
      Previous value: -"YYYY-MM-DD format"New value: +"Date the vehicle's next scheduled service is due, in YYYY-MM-DD format. Omit to leave unchanged, or send an empty string to clear it."
    • addedInput schema / properties / serviceDueDate / examples
      Added value: +[
+  "2027-01-20"
+]
    • changedInput schema / properties / taxDueDate / description
      Previous value: -"YYYY-MM-DD format"New value: +"Date the vehicle's road tax is next due, in YYYY-MM-DD format. Omit to leave unchanged, or send an empty string to clear it."
    • addedInput schema / properties / taxDueDate / examples
      Added value: +[
+  "2026-09-01"
+]
    • addedInput schema / properties / vin / description
      Added value: +"Vehicle Identification Number: a 17-character alphanumeric code unique to the vehicle. Omit to leave unchanged, or send an empty string to clear it."
    • addedInput schema / properties / vin / examples
      Added value: +[
+  "1HGCM82633A004352"
+]
    • addedInput schema / properties / year / description
      Added value: +"Model year of the vehicle. Must be between 1900 and 2100. Omit to leave unchanged."
    • addedInput schema / properties / year / examples
      Added value: +[
+  2021
+]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and destructiveHint=false, so the description carries the responsibility of explaining actual behavior. It adds valuable transparency: only sent fields change, and empty strings clear text/due-date fields. This goes beyond what the annotations alone reveal about the update semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler. The core purpose leads, followed immediately by the most important behavioral nuance. Every word earns its place.

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

Completeness4/5

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

Given full parameter documentation, an output schema, and annotations, the description provides the essential missing glue: partial-update behavior and clearing semantics. It could mention that the id must come from list_vehicles, but the schema already states that, so no critical gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds cross-parameter meaning not present in any individual parameter description: empty strings clear text and due-date fields. This is a significant extra semantic rule that helps the agent use parameters correctly.

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?

The description uses a specific verb+resource ('Update a vehicle') and adds a clarifying behavioral scope: 'Only the fields you send change.' This distinguishes it clearly from sibling tools like create_vehicle, delete_vehicle, and list_vehicles without needing to consult their schemas.

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

Usage Guidelines4/5

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

The description gives clear usage context by explaining partial-update semantics and the empty-string clearing rule, which tell the agent how to approach an update. It does not explicitly name alternatives or state when not to use the tool, but the 'update' framing and sibling names make the decision obvious enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All haus toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources