haus

create_document

Create a document (passport, insurance, certificate, warranty, license, other)

Input Schema

TableJSON Schema

Name	Required	Description
`fee`	No	The cost associated with the document, e.g. a renewal or issuance fee.
`notes`	No	Free-text notes about the document.
`title`	No	A custom title for the document. If omitted, one is derived from the document type and number, e.g. 'Passport - 512345678'.
`documentType`	Yes	The kind of document being stored.
`documentNumber`	No	The document's reference or serial number, e.g. a passport number or insurance policy number.
`issuingAuthority`	No	The organization or authority that issued the document.
`renewalCronExpression`	No	Reserved for a future renewal-reminder schedule. Currently accepted but not persisted or acted on by document creation — has no effect yet.

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.

Changed14 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "documentNumber": "512345678",
+    "documentType": "Passport",
+    "fee": {
+      "currencyCode": "GBP",
+      "value": 8250
+    },
+    "issuingAuthority": "HM Passport Office",
+    "notes": "Renew before the next family trip.",
+    "title": "UK Passport"
+  }
+]

addedInput schema / properties / documentNumber / description

Added value: +"The document's reference or serial number, e.g. a passport number or insurance policy number."

addedInput schema / properties / documentNumber / examples
```
Added value: +[
+  "512345678"
+]
```
addedInput schema / properties / documentType / description
```
Added value: +"The kind of document being stored."
```
addedInput schema / properties / documentType / examples
```
Added value: +[
+  "Passport"
+]
```

addedInput schema / properties / fee / description

Added value: +"The cost associated with the document, e.g. a renewal or issuance fee."

addedInput schema / properties / fee / properties / currencyCode / examples
```
Added value: +[
+  "GBP"
+]
```
addedInput schema / properties / fee / properties / value / examples
```
Added value: +[
+  8250
+]
```

addedInput schema / properties / issuingAuthority / description

Added value: +"The organization or authority that issued the document."

addedInput schema / properties / issuingAuthority / examples
```
Added value: +[
+  "HM Passport Office"
+]
```

addedInput schema / properties / notes / description

Added value: +"Free-text notes about the document."

changedInput schema / properties / renewalCronExpression / description

Previous value: -"Cron expression for renewal"New value: +"Reserved for a future renewal-reminder schedule. Currently accepted but not persisted or acted on by document creation — has no effect yet."

addedInput schema / properties / title / description

Added value: +"A custom title for the document. If omitted, one is derived from the document type and number, e.g. 'Passport - 512345678'."

addedInput schema / properties / title / examples
```
Added value: +[
+  "UK Passport"
+]
```

Changed1 schema field changedJul 3, 2026
- addedInput schema / properties / title
```
Added value: +{
+  "type": "string"
+}
```
First observedJun 30, 2026

TDQS

A3.6/5.0

Behavior2/5

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

Annotations already indicate a write operation (readOnlyHint=false) and non-destructive behavior (destructiveHint=false). The description adds no further behavioral context, such as persistence guarantees, required permissions, or the notable fact that renewalCronExpression is currently ignored (documented only in the schema).

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 a single, concise sentence that immediately states the action and scope. It contains no filler or redundant information, making it highly efficient and front-loaded.

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 the rich input schema, output schema, and annotations, the description adequately supports tool selection. It does not explain all side effects, but the schema covers parameter semantics and the output schema likely defines return values, making the description sufficient for a well-annotated create tool.

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?

The input schema provides detailed descriptions for all 7 parameters, including the nested fee object and the ineffective renewalCronExpression, giving 100% coverage. The description only echoes the document type enum, adding no semantic value beyond the schema, so the baseline of 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?

The description uses the specific verb 'Create' and identifies the resource as 'document', then lists valid document types (passport, insurance, certificate, warranty, license, other). This clearly distinguishes it from sibling tools that create other entities (appliances, contacts, tasks) and from document-related tools like update_document or delete_document.

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 usage through the verb and document type enumeration, but provides no explicit guidance on when to use this tool versus alternatives. It does not mention scenarios like updating existing documents or listing documents, leaving the agent to infer the intended use case.

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?