Skip to main content
Glama

haus

by app.onehaus
OverviewDiscussionsAdmin

update_pet

Update a pet's name, microchip number, date of birth, notes, or its linked vet contact and insurance document. Only the fields you send change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPet id from list_pets.
nameNoNew name.
notesNoFreeform notes.
dateOfBirthNoDate of birth, YYYY-MM-DD. Empty string clears it.
vetContactIdNoVet contact id from create_contact.
microchipNumberNoNew microchip number.
insuranceDocumentIdNoInsurance document id from create_document.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
titleNo
messageNo
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / dateOfBirth / description
      Previous 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."New value: +"Date of birth, YYYY-MM-DD. Empty string clears it."
    • changedInput schema / properties / id / description
      Previous value: -"ID of the pet to update."New value: +"Pet id from list_pets."
    • changedInput schema / properties / insuranceDocumentId / description
      Previous value: -"ID of a previously created document containing the pet's insurance policy. Omit to leave unchanged."New value: +"Insurance document id from create_document."
    • changedInput schema / properties / microchipNumber / description
      Previous value: -"New microchip identification number. Omit to leave unchanged."New value: +"New microchip number."
    • changedInput schema / properties / name / description
      Previous value: -"New name for the pet. Omit to leave unchanged."New value: +"New name."
    • changedInput schema / properties / notes / description
      Previous value: -"Freeform notes about the pet. Omit to leave unchanged."New value: +"Freeform notes."
    • changedInput schema / properties / vetContactId / description
      Previous value: -"ID of a previously created contact for the pet's vet. Omit to leave unchanged."New value: +"Vet contact id from create_contact."
  2. 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"
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The statement 'Only the fields you send change' clearly discloses partial-update behavior, adding value beyond the annotations (readOnlyHint=false, destructiveHint=false). It also clarifies that linked vet contact and insurance document references are updatable. No contradiction with 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 brief sentences with no filler. The first sentence is front-loaded with the verb and resource, and the second adds essential behavioral nuance without redundancy.

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?

All updatable categories are covered, including linked vet contact and insurance document, and the partial-update behavior is stated. The id source is handled in the schema, and an output schema exists, so the description is sufficiently complete for a 7-parameter update tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds important meaning by specifying that omitted fields remain unchanged and grouping vetContactId and insuranceDocumentId as linked references, which is not explicit in the schema.

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 names a specific action (Update), a resource (pet), and enumerates the exact fields that can be changed, making the tool's function unambiguous. It also distinguishes itself from create_pet and delete_pet by focusing on modification of existing pets.

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 update semantics imply use on an existing pet, but the description does not explicitly contrast with create_pet or delete_pet, nor does it state when not to use the tool. The context is sufficient, but exclusions and alternatives are left to inference.

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