haus

create_contact

Add a contact to the address book. Only firstName is required; address, date of birth, notes and the birthday-present flag can follow via update_contact.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	No	Email address.
`notes`	No	Free-text notes.
`phone`	No	Phone number, any format.
`address`	No	Postal address.
`lastName`	No	Last (family) name.
`firstName`	Yes	First name. The only required field.
`dateOfBirth`	No	Date of birth, YYYY-MM-DD. Drives the birthday reminder.
`displayName`	No	Name to show instead of first/last, e.g. a nickname or company.
`prepareBirthdayPresent`	No	Whether to flag a birthday present for them.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedSep 8, 2026

changedInput schema / properties / address / description

Previous value: -"The contact's postal address."New value: +"Postal address."

changedInput schema / properties / address / properties / countryCode / description

Previous value: -"Country code (e.g., GB, US)"New value: +"ISO country code, e.g. GB."

changedInput schema / properties / address / properties / line1 / description

Previous value: -"First line of the address, typically house number and street."New value: +"Line 1, typically number and street."

addedInput schema / properties / address / properties / line1 / examples
```
Added value: +[
+  "12 Baker Street"
+]
```

changedInput schema / properties / address / properties / line2 / description

Previous value: -"Second line of the address, e.g. apartment, suite, or unit."New value: +"Line 2, e.g. apartment or unit."

addedInput schema / properties / address / properties / line2 / examples
```
Added value: +[
+  "Flat 3"
+]
```

changedInput schema / properties / address / properties / line3 / description

Previous value: -"Third line of the address, e.g. town or city."New value: +"Line 3, e.g. town or city."

addedInput schema / properties / address / properties / line3 / examples
```
Added value: +[
+  "London"
+]
```

changedInput schema / properties / dateOfBirth / description

Previous value: -"YYYY-MM-DD format"New value: +"Date of birth, YYYY-MM-DD. Drives the birthday reminder."

changedInput schema / properties / displayName / description

Previous value: -"An alternate name to show for the contact instead of first/last, e.g. a nickname, company name, or role."New value: +"Name to show instead of first/last, e.g. a nickname or company."

addedInput schema / properties / displayName / examples
```
Added value: +[
+  "Sarah from book club"
+]
```

changedInput schema / properties / email / description

Previous value: -"The contact's email address."New value: +"Email address."

changedInput schema / properties / firstName / description

Previous value: -"The contact's first name. The only required field."New value: +"First name. The only required field."

changedInput schema / properties / lastName / description

Previous value: -"The contact's last (family) name."New value: +"Last (family) name."

addedInput schema / properties / lastName / examples
```
Added value: +[
+  "Jones"
+]
```

changedInput schema / properties / notes / description

Previous value: -"Free-text notes about the contact."New value: +"Free-text notes."

addedInput schema / properties / notes / examples

Added value: +[
+  "Met at the neighbourhood BBQ."
+]

changedInput schema / properties / phone / description

Previous value: -"The contact's phone number, in any format."New value: +"Phone number, any format."

changedInput schema / properties / prepareBirthdayPresent / description

Previous value: -"Whether to prepare a birthday present for this contact"New value: +"Whether to flag a birthday present for them."

addedInput schema / properties / prepareBirthdayPresent / examples
```
Added value: +[
+  true
+]
```

Changed18 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "address": {
+      "countryCode": "GB",
+      "line1": "12 Baker Street",
+      "postalCode": "NW1 6XE"
+    },
+    "dateOfBirth": "1990-05-15",
+    "email": "sarah.jones@example.com",
+    "firstName": "Sarah",
+    "lastName": "Jones",
+    "notes": "Met at the neighbourhood BBQ.",
+    "phone": "+44 7911 123456",
+    "prepareBirthdayPresent": true
+  }
+]

addedInput schema / properties / address / description
```
Added value: +"The contact's postal address."
```
addedInput schema / properties / address / properties / countryCode / examples
```
Added value: +[
+  "GB"
+]
```

addedInput schema / properties / address / properties / line1 / description

Added value: +"First line of the address, typically house number and street."

addedInput schema / properties / address / properties / line2 / description

Added value: +"Second line of the address, e.g. apartment, suite, or unit."

addedInput schema / properties / address / properties / line3 / description
```
Added value: +"Third line of the address, e.g. town or city."
```
addedInput schema / properties / address / properties / postalCode / description
```
Added value: +"Postal or ZIP code."
```
addedInput schema / properties / address / properties / postalCode / examples
```
Added value: +[
+  "NW1 6XE"
+]
```
addedInput schema / properties / dateOfBirth / examples
```
Added value: +[
+  "1990-05-15"
+]
```

addedInput schema / properties / displayName / description

Added value: +"An alternate name to show for the contact instead of first/last, e.g. a nickname, company name, or role."

addedInput schema / properties / email / description
```
Added value: +"The contact's email address."
```

addedInput schema / properties / email / examples

Added value: +[
+  "sarah.jones@example.com"
+]

addedInput schema / properties / firstName / description

Added value: +"The contact's first name. The only required field."

addedInput schema / properties / firstName / examples
```
Added value: +[
+  "Sarah"
+]
```
addedInput schema / properties / lastName / description
```
Added value: +"The contact's last (family) name."
```

addedInput schema / properties / notes / description

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

addedInput schema / properties / phone / description

Added value: +"The contact's phone number, in any format."

addedInput schema / properties / phone / examples
```
Added value: +[
+  "+44 7911 123456"
+]
```

First observedJun 30, 2026

TDQS

A4/5.0

Behavior3/5

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

The description adds a useful behavioral note beyond the annotations: the create operation can be minimal, and optional fields can be supplied later via update_contact. However, it does not disclose side effects, duplicate behavior, or validation outcomes; the annotations only indicate a mutating but non-destructive operation.

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 concise, front-loaded sentences with no filler. The main purpose comes first, followed by the key requirement and update path, making it easy for an agent to parse quickly.

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 sibling context, the description is largely sufficient. It correctly highlights the single required field and the update route for optional fields, though the enumerated optional-fields list is a subset and could have clarified that all other fields are also optional at creation.

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 already covers all 9 parameters with descriptions, so the baseline is 3. The description reinforces that firstName is the only required field and names a few optional fields, but it does not add meaningful semantic detail beyond what the schema already provides.

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 action ('Add a contact to the address book') and identifies the resource as a contact, distinguishing it from the many other create_* sibling tools. It also points to update_contact, reinforcing what this specific tool is for.

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: only firstName is required for creation, and optional fields can be added later via update_contact. It names the relevant alternative tool, though it does not explicitly cover when not to use create_contact beyond that.

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

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

Need Help?