haus

create_pet

Add a pet, optionally with its microchip number and date of birth, and links to an existing contact as vet and document as insurance. Returns the new pet's id.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Name.
`notes`	No	Freeform notes, e.g. diet or medical history.
`dateOfBirth`	No	Date of birth, YYYY-MM-DD.
`vetContactId`	No	Vet contact id from create_contact.
`microchipNumber`	No	Microchip number.
`insuranceDocumentId`	No	Insurance document id from create_document.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 8, 2026

changedInput schema / properties / dateOfBirth / description

Previous value: -"The pet's date of birth, in YYYY-MM-DD format."New value: +"Date of birth, YYYY-MM-DD."

changedInput schema / properties / insuranceDocumentId / description

Previous value: -"ID of a previously created document containing the pet's insurance policy."New value: +"Insurance document id from create_document."

changedInput schema / properties / microchipNumber / description

Previous value: -"Microchip identification number, used to reunite a lost pet with its household."New value: +"Microchip number."

changedInput schema / properties / name / description

Previous value: -"The pet's name."New value: +"Name."

changedInput schema / properties / notes / description

Previous value: -"Freeform notes about the pet, e.g. dietary needs or medical history."New value: +"Freeform notes, e.g. diet or medical history."

changedInput schema / properties / vetContactId / description

Previous value: -"ID of a previously created contact for the pet's vet."New value: +"Vet contact id from create_contact."

Changed13 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "dateOfBirth": "2021-06-15",
+    "microchipNumber": "985141000123456",
+    "name": "Bella",
+    "notes": "Allergic to chicken; on prescription food."
+  }
+]

changedInput schema / properties / dateOfBirth / description

Previous value: -"YYYY-MM-DD format"New value: +"The pet's date of birth, in YYYY-MM-DD format."

addedInput schema / properties / dateOfBirth / examples
```
Added value: +[
+  "2021-06-15"
+]
```

changedInput schema / properties / insuranceDocumentId / description

Previous value: -"Document ID of insurance policy"New value: +"ID of a previously created document containing the pet's insurance policy."

addedInput schema / properties / insuranceDocumentId / examples
```
Added value: +[
+  "doc_1a2b3c4d5e6f"
+]
```

addedInput schema / properties / microchipNumber / description

Added value: +"Microchip identification number, used to reunite a lost pet with its household."

addedInput schema / properties / microchipNumber / examples
```
Added value: +[
+  "985141000123456"
+]
```
addedInput schema / properties / name / description
```
Added value: +"The pet's name."
```
addedInput schema / properties / name / examples
```
Added value: +[
+  "Bella"
+]
```

addedInput schema / properties / notes / description

Added value: +"Freeform notes about the pet, e.g. dietary needs or medical history."

addedInput schema / properties / notes / examples

Added value: +[
+  "Allergic to chicken; on prescription food."
+]

changedInput schema / properties / vetContactId / description

Previous value: -"Contact ID of the vet"New value: +"ID of a previously created contact for the pet's vet."

addedInput schema / properties / vetContactId / examples
```
Added value: +[
+  "contact_5e6f7a8b9c0d"
+]
```

First observedJun 30, 2026

TDQS

A4/5.0

Behavior4/5

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

The description discloses relevant behavioral details beyond the annotations: it creates a new pet, optionally associates existing contact/document resources as vet and insurance, and returns the new pet's id. This adds useful context about relationships and return value, even though error conditions are not discussed.

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, front-loaded sentence that communicates the action, optional parameters, relationship semantics, and return value without wasted words. Every clause 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?

For a create tool with one required parameter, full schema coverage, and an output schema, the description plus schema provide enough to invoke the tool correctly. It could mention explicit constraints like unique microchip handling, but that is not essential for basic correct invocation.

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 the baseline is 3. The description paraphrases optionality and the vet/insurance link roles, but it does not add substantive meaning beyond the schema's existing field descriptions and the required field list.

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 and resource ('Add a pet') and goes on to summarize the optional fields and links to contact/document, making the tool's purpose immediately clear. It is also distinguishable from sibling tools because it is the only one about creating a pet.

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 clearly implies the tool is for creating new pets, but it does not explicitly state when to use it versus alternatives like update_pet or delete_pet. No when-not or alternative-routing guidance is provided, though the creation context is reasonably inferable.

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?