Skip to main content
Glama

haus

by app.onehaus

update_pet

Update a pet. Omitted fields unchanged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the pet to update.
nameNoNew name for the pet. Omit to leave unchanged.
notesNoFreeform notes about the pet. Omit to leave unchanged.
dateOfBirthNoThe pet's date of birth, in YYYY-MM-DD format. Omit or send null to leave unchanged, send an empty string to clear it.
vetContactIdNoID of a previously created contact for the pet's vet. Omit to leave unchanged.
microchipNumberNoNew microchip identification number. Omit to leave unchanged.
insuranceDocumentIdNoID of a previously created document containing the pet's insurance policy. Omit to leave unchanged.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
titleNo
messageNo
variantNo

Schema Changelog

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

  1. Changed15 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "01933f9c-7a2b-7c3d-8e4f-1a2b3c4d5e6f",
+    "notes": "Started prescription diet on vet's advice."
+  }
+]
    • changedInput schema / properties / dateOfBirth / description
      Previous value: -"YYYY-MM-DD format"New value: +"The pet's date of birth, in YYYY-MM-DD format. Omit or send null to leave unchanged, send an empty string to clear it."
    • addedInput schema / properties / dateOfBirth / examples
      Added value: +[
+  "2021-06-15"
+]
    • addedInput schema / properties / id / description
      Added value: +"ID of the pet to update."
    • addedInput schema / properties / id / examples
      Added value: +[
+  "01933f9c-7a2b-7c3d-8e4f-1a2b3c4d5e6f"
+]
    • 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. Omit to leave unchanged."
    • addedInput schema / properties / insuranceDocumentId / examples
      Added value: +[
+  "doc_1a2b3c4d5e6f"
+]
    • addedInput schema / properties / microchipNumber / description
      Added value: +"New microchip identification number. Omit to leave unchanged."
    • addedInput schema / properties / microchipNumber / examples
      Added value: +[
+  "985141000123456"
+]
    • addedInput schema / properties / name / description
      Added value: +"New name for the pet. Omit to leave unchanged."
    • addedInput schema / properties / name / examples
      Added value: +[
+  "Bella"
+]
    • addedInput schema / properties / notes / description
      Added value: +"Freeform notes about the pet. Omit to leave unchanged."
    • 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. Omit to leave unchanged."
    • addedInput schema / properties / vetContactId / examples
      Added value: +[
+  "contact_5e6f7a8b9c0d"
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate the operation is not read-only and not destructive. The description adds valuable behavioral context by specifying 'Omitted fields unchanged', which communicates an idempotent partial-update semantic not visible from annotations alone. This goes beyond the structured data.

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 zero filler. The first sentence states the purpose, and the second conveys the critical behavioral rule. It is appropriately sized and front-loaded for quick parsing.

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 (100% param coverage, examples) and the presence of an output schema, the description does not need to explain return values or parameter details. The only missing context is error behavior for nonexistent IDs and prerequisites, but the description covers the essential partial-update semantics. This is complete for a straightforward update 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?

Schema description coverage is 100%, and every parameter description already states 'Omit to leave unchanged' (or similar). The description's 'Omitted fields unchanged' is a useful summary but adds no new information beyond what the schema provides. The baseline of 3 applies because the schema fully documents parameters.

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 immediately states 'Update a pet' with a specific verb and resource, distinguishing it from create_pet, delete_pet, and list_pets. It adds the key detail 'Omitted fields unchanged', which clarifies the tool's partial-update behavior and further differentiates it from full-replacement update tools.

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 the tool is for modifying an existing pet, but it does not explicitly state when to use it versus alternatives such as create_pet or delete_pet. There is no mention of prerequisites like the pet existing or exclusionary conditions, so guidance is minimal but not misleading.

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