Skip to main content
Glama

Update contact

update_contact

Update a personal contact by ID, changing only supplied fields; use an empty string to clear a field or new emails to replace all addresses.

Instructions

Update a personal contact. Only given fields change; an empty string clears a field and emails replaces all addresses.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "update_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesContact ID
notesNo
emailsNoUp to three addresses ("jane@contoso.com" or "Jane Doe <jane@contoso.com>")
companyNo
surnameNoLast name
jobTitleNo
nicknameNo
givenNameNoFirst name
homePhoneNo
categoriesNo
departmentNo
middleNameNo
displayNameNoDisplay name (default "givenName surname")
homeAddressNoPostal address
mobilePhoneNo
businessPhoneNo
officeLocationNo
businessAddressNoPostal address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations only declare that this is a non-read-only, non-destructive, closed-world mutation. The description goes well beyond that by disclosing patch semantics ("only given fields change"), the empty-string clearing convention, and that emails replaces rather than appends to all addresses — all behavior an agent cannot get from the annotations. It omits permission requirements and error behavior for a missing id.

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 short sentences with the update semantics front-loaded and the two field-level rules packed into a single clause. Nothing is redundant with the title or schema, and every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-parameter mutation with nested objects and no output schema, the description covers the crucial patch and clear semantics but leaves the merge-vs-replace behavior for nested addresses and array fields unstated. There is also no mention of what the call returns or what happens when the id does not exist.

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 only 39%, so the description must compensate, and it does for the two most error-prone behaviors: empty-string clearing and the replace-all semantics of emails. It does not explain how the clearing rule applies to non-string parameters such as categories or the nested address objects, leaving several of the 18 parameters under-specified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Update a personal contact"), which clearly separates it from create_contact, delete_contact, and get_contact among the siblings. It does not explicitly name a sibling or clarify scope boundaries (e.g. personal vs. other contact types), so it stops short of a 5.

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?

Usage is only implied by the verb "update" and the partial-update note; the description never states when to use this instead of create_contact or how it relates to batch or list tools. There are no explicit preconditions, so an agent must infer the when-to-use case from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.