haus

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

Name	Required	Description
`vin`	No	Vehicle Identification Number: a 17-character alphanumeric code unique to the vehicle.
`make`	No	Manufacturer of the vehicle, e.g. 'Toyota'.
`year`	No	Model year of the vehicle. Must be between 1900 and 2100.
`model`	No	Model name of the vehicle, e.g. 'Corolla'.
`notes`	No	Free-text notes about the vehicle.
`colour`	No	Colour of the vehicle.
`motDueDate`	No	Date the next MOT (roadworthiness test) is due, in YYYY-MM-DD format.
`taxDueDate`	No	Date the vehicle's road tax is next due, in YYYY-MM-DD format.
`registration`	No	The vehicle's registration/licence plate as shown on the plate. Free-text; format varies by country.
`serviceDueDate`	No	Date the vehicle's next scheduled service is due, in YYYY-MM-DD format.
`insuranceDocumentId`	No	Document ID of insurance policy

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`title`	No
`message`	No
`variant`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed20 schema fields changedJul 14, 2026

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
+]
```

First observedJun 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations indicate this is a write operation (readOnlyHint false) but not destructive. The description adds useful behavioral context beyond annotations by noting 'All fields are optional' and specifying the scope of data tracked. This is meaningful but does not go into side effects or prerequisites, which is acceptable given the annotations.

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?

The description is two short sentences with no redundancy. The first sentence front-loads the action and resource, and the second adds a key constraint (all fields optional). Every word contributes to clarity, making it an ideal length.

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 plus the complete schema and output schema provide sufficient context for an agent to select and invoke the tool correctly. It lacks explicit guidance on prerequisites, such as whether the household must already exist or if the insurance document ID must reference an existing document, but given the richness of structured data, this is a minor gap.

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% for all 11 parameters, so the description bears little burden for explaining parameters. It mentions categories like registration/VIN and due dates, but this does not add significant semantic value beyond the schema's own detailed descriptions. The optionality note is helpful but not parameter-specific.

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 clearly states the tool's function: 'Create a vehicle record for the household' with a specific verb and resource. It also lists what the record tracks (details, registration/VIN, insurance document, MOT/tax/service due dates), distinguishing it from sibling tools like update_vehicle, delete_vehicle, and list_vehicles.

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

Usage Guidelines3/5

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

The description implies use for adding a new vehicle to a household but does not explicitly state when to use this tool versus update_vehicle or other create tools. It lacks exclusions or explicit alternative guidance, though the context of 'create a vehicle record' makes the primary use case evident.

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

All haus 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

A3.9/5.0

Disambiguation5/5

Each tool targets a distinct resource and action, with clear descriptions separating similar-sounding tools like create_calendar_event vs create_recurring_calendar_event. Shopping list operations (add, buy, remove, update) are clearly delineated.

Naming Consistency5/5

All tools follow a verb_noun snake_case pattern: create_*, list_*, update_*, delete_*, get_*, etc. Even special operations like store_memory, recall_memory, and skip_recommendation fit the pattern.

Tool Count1/5

With 68 tools, this server vastly exceeds a reasonable scope; the instruction manual indicates 50+ tools is an extreme mismatch. The breadth suggests the server should be split into focused sub-servers (tasks, shopping, calendar, etc.) rather than a single monolithic interface.

Completeness5/5

The tool surface covers full CRUD/lifecycle for all major resources: tasks, shopping, calendar, contacts, documents, appliances, vehicles, pets, recipes, meal plans, subscriptions, and memories. Additional features like house review, weather, and profile round out the household management domain.

Resources

Need Help?