Skip to main content
Glama

haus

by app.onehaus
OverviewDiscussionsAdmin

update_contact

Update a contact by id. Only the fields supplied are changed; omitted fields keep their current value (dateOfBirth is the exception: an empty string explicitly clears it).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContact id from create_contact or list_contacts.
emailNoEmail address.
notesNoFree-text notes.
phoneNoPhone number, any format.
addressNoPostal address. Replaces the stored one outright.
lastNameNoLast (family) name.
firstNameNoFirst name.
dateOfBirthNoDate of birth, YYYY-MM-DD. Empty string clears it.
displayNameNoName to show instead of first/last, e.g. a nickname or company.
prepareBirthdayPresentNoWhether to flag a birthday present for them.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
titleNo
messageNo
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"The contact's postal address. Omit to leave unchanged; when supplied, replaces the whole address."New value: +"Postal address. Replaces the stored one outright."
    • 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. Omit or pass null to leave unchanged; pass an empty string to clear it."New value: +"Date of birth, YYYY-MM-DD. Empty string clears it."
    • 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. Omit to leave unchanged."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. Omit to leave unchanged."New value: +"Email address."
    • changedInput schema / properties / firstName / description
      Previous value: -"The contact's first name. Omit to leave unchanged."New value: +"First name."
    • addedInput schema / properties / firstName / examples
      Added value: +[
+  "Sarah"
+]
    • changedInput schema / properties / id / description
      Previous value: -"The id of the contact to update, as returned by create_contact or list_contacts."New value: +"Contact id from create_contact or list_contacts."
    • changedInput schema / properties / lastName / description
      Previous value: -"The contact's last (family) name. Omit to leave unchanged."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. Omit to leave unchanged."New value: +"Free-text notes."
    • addedInput schema / properties / notes / examples
      Added value: +[
+  "Prefers texts over calls."
+]
    • changedInput schema / properties / phone / description
      Previous value: -"The contact's phone number, in any format. Omit to leave unchanged."New value: +"Phone number, any format."
    • changedInput schema / properties / prepareBirthdayPresent / description
      Previous value: -"Whether to prepare a birthday present for this contact. Omit to leave unchanged."New value: +"Whether to flag a birthday present for them."
    • addedInput schema / properties / prepareBirthdayPresent / examples
      Added value: +[
+  true
+]
  2. Changed21 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "01928e4a7d3f7b9ac1e3f6d8b2a4c710",
+    "notes": "Prefers texts over calls.",
+    "phone": "+44 7911 123456"
+  }
+]
    • addedInput schema / properties / address / description
      Added value: +"The contact's postal address. Omit to leave unchanged; when supplied, replaces the whole 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"
+]
    • changedInput schema / properties / dateOfBirth / description
      Previous value: -"YYYY-MM-DD format"New value: +"YYYY-MM-DD format. Omit or pass null to leave unchanged; pass an empty string to clear it."
    • 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. Omit to leave unchanged."
    • addedInput schema / properties / email / description
      Added value: +"The contact's email address. Omit to leave unchanged."
    • addedInput schema / properties / email / examples
      Added value: +[
+  "sarah.jones@example.com"
+]
    • addedInput schema / properties / firstName / description
      Added value: +"The contact's first name. Omit to leave unchanged."
    • addedInput schema / properties / id / description
      Added value: +"The id of the contact to update, as returned by create_contact or list_contacts."
    • addedInput schema / properties / id / examples
      Added value: +[
+  "01928e4a7d3f7b9ac1e3f6d8b2a4c710"
+]
    • addedInput schema / properties / lastName / description
      Added value: +"The contact's last (family) name. Omit to leave unchanged."
    • addedInput schema / properties / notes / description
      Added value: +"Free-text notes about the contact. Omit to leave unchanged."
    • addedInput schema / properties / phone / description
      Added value: +"The contact's phone number, in any format. Omit to leave unchanged."
    • addedInput schema / properties / phone / examples
      Added value: +[
+  "+44 7911 123456"
+]
    • changedInput schema / properties / prepareBirthdayPresent / description
      Previous value: -"Whether to prepare a birthday present for this contact"New value: +"Whether to prepare a birthday present for this contact. Omit to leave unchanged."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only convey that this is a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds essential behavior beyond that: supplied fields are changed, omitted fields retain their values, and dateOfBirth has a clear-if-empty exception. This is exactly the kind of nuance an agent needs to avoid destructive mistakes. It doesn't cover error cases, but the main behavioral traits are disclosed.

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?

Two sentences with zero wasted words. The core action is front-loaded, the partial-update rule follows immediately, and the single exception is in a parenthetical aside. Every sentence 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?

The tool is well-covered overall: an output schema exists so return values need no explanation, annotations cover the safety profile, and the description covers the critical merge semantics. Minor gaps remain — no mention of what happens when the id doesn't exist or whether updates are immediately persisted — but these are modest given the surrounding structured context.

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 nevertheless adds meaning beyond the schema: the universal rule that omitted fields keep their current value is a parameter-level semantic applying to all optional fields. The dateOfBirth-empty-string nuance is duplicated in the schema, but the global patch behavior is a genuine addition that shapes how every parameter should be interpreted.

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 states a specific verb ('Update'), a clear resource ('a contact'), and the targeting mechanism ('by id'). This cleanly distinguishes it from the sibling tools create_contact, delete_contact, and list_contacts — an agent can tell them apart without opening schemas.

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 operational context: it's a partial/patch-style update rather than a full replace, which directly tells the agent how to construct the call (send only the fields to change). It doesn't explicitly name alternatives or state 'use create_contact for new contacts,' but the update-by-id phrasing plus the sibling set makes the main usage boundary clear.

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