Skip to main content
Glama

haus

by app.onehaus
OverviewDiscussionsAdmin

create_vehicle

Create a vehicle record for the household to track its details, registration and VIN, insurance document, and upcoming MOT/tax/service due dates. All fields are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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 create_document or list_documents.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
titleNo
messageNo
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedInput schema / properties / colour / description
      Previous value: -"Colour of the vehicle."New value: +"Colour."
    • changedInput schema / properties / insuranceDocumentId / description
      Previous value: -"Document ID of insurance policy"New value: +"Insurance document id from create_document or list_documents."
    • addedInput schema / properties / insuranceDocumentId / examples
      Added value: +[
+  "01928e4a7d3f7b9ac1e3f6d8b2a4c710"
+]
    • changedInput schema / properties / make / description
      Previous value: -"Manufacturer of the vehicle, e.g. 'Toyota'."New value: +"Manufacturer, e.g. 'Toyota'."
    • changedInput schema / properties / model / description
      Previous value: -"Model name of the vehicle, e.g. 'Corolla'."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."New value: +"Next MOT (roadworthiness test) due date, YYYY-MM-DD."
    • changedInput schema / properties / notes / description
      Previous value: -"Free-text notes about the vehicle."New value: +"Free-text notes."
    • addedInput schema / properties / notes / examples
      Added value: +[
+  "Winter tyres fitted"
+]
    • changedInput schema / properties / registration / description
      Previous value: -"The vehicle's registration/licence plate as shown on the plate. Free-text; format varies by country."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."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."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."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."New value: +"Model year, 1900-2100."
  2. Changed20 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "colour": "Blue",
+    "make": "Toyota",
+    "model": "Corolla",
+    "motDueDate": "2026-11-15",
+    "notes": "Winter tyres fitted",
+    "registration": "AB21 CDE",
+    "serviceDueDate": "2027-01-20",
+    "taxDueDate": "2026-09-01",
+    "vin": "1HGCM82633A004352",
+    "year": 2021
+  }
+]
    • addedInput schema / properties / colour / description
      Added value: +"Colour of the vehicle."
    • addedInput schema / properties / colour / examples
      Added value: +[
+  "Blue"
+]
    • addedInput schema / properties / make / description
      Added value: +"Manufacturer of the vehicle, e.g. 'Toyota'."
    • addedInput schema / properties / make / examples
      Added value: +[
+  "Toyota"
+]
    • addedInput schema / properties / model / description
      Added value: +"Model name of the vehicle, e.g. 'Corolla'."
    • 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."
    • addedInput schema / properties / motDueDate / examples
      Added value: +[
+  "2026-11-15"
+]
    • addedInput schema / properties / notes / description
      Added value: +"Free-text notes about the vehicle."
    • addedInput schema / properties / registration / description
      Added value: +"The vehicle's registration/licence plate as shown on the plate. Free-text; format varies by country."
    • 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."
    • 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."
    • 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."
    • 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."
    • addedInput schema / properties / year / examples
      Added value: +[
+  2021
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the write intent is consistent. The description adds useful behavioral context by stating all fields are optional and listing the categories of information tracked. No contradictions found.

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 sentences, front-loaded with the action and resource. The second sentence adds the key constraint that all fields are optional. No filler or redundant content.

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?

The description is sufficient for an agent to understand the tool's purpose and optionality. With a fully described schema, output schema present, and annotations aligned, no critical information is missing. It could be slightly more complete by naming alternatives, but that is already covered in the usage dimension.

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%, so every parameter is already documented in the schema with type, example, and description. The tool description only groups parameters conceptually (details, VIN, insurance, due dates) without adding new semantic detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

The description states a specific verb and resource: 'Create a vehicle record for the household'. It also enumerates what the record tracks, making the intent clear. While it doesn't explicitly contrast with sibling tools like update_vehicle or list_vehicles, the create verb is unambiguous.

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 context: use this when you need to create a new vehicle record for the household. It notes that all fields are optional, which helps set expectations. However, it doesn't explicitly mention when not to use it or point to alternatives like update_vehicle or delete_vehicle.

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