Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Update contact

update_contact

Edit a stored contact by ID, changing only named fields while preserving the rest. Add or remove emails, phones, addresses, and roles, or set the preferred email without resending the record.

Instructions

Edit a stored contact by id, changing only the fields you name — everything else is kept, so you never have to read the record and re-send it. Set name, organization, birthday or note directly ("" clears all but the name); add or remove email addresses, phone numbers, postal addresses and roles with the added…/removed… lists; a role is what the person is to the user ("lawyer"), recorded only when the user said or confirmed it, and search_contacts then finds them by it; correct one component of a stored postal address with updatedPostalAddresses; mark the address mail should go to with preferredEmail. Find the contact_id and the [a0]-style handles with search_contacts. To fold two contacts that are the same person into one, use merge_contacts instead.

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": {
      "contactId": "<contactId>"
    },
    "name": "update_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew display name. Omit to keep the stored one.
noteNoNew note, replacing every note stored on the contact; `""` clears them. Omit to keep them. (A contact edited elsewhere can carry more than one.)
birthdayNoNew birthday as `YYYY-MM-DD`, or `--MM-DD` when the year is unknown; `""` clears it. Omit to keep it.
contactIdYesThe contact id, as printed by search_contacts under `contact_id`.
addedRolesNoRoles to add: what the person is to the user ("lawyer"), as the user said or confirmed it. Never inferred from mail.
addedEmailsNoEmail addresses to add to the contact.
addedPhonesNoPhone numbers to add to the contact.
organizationNoNew organization; `""` clears it. Omit to keep the stored one.
removedRolesNoRoles to remove (case-insensitive).
removedEmailsNoEmail addresses to remove (case-insensitive).
removedPhonesNoPhone numbers to remove, each given either as its `[p0]` handle or as the number itself.
preferredEmailNoThe address mail to this contact should go to: one already on the contact or added in this call. search_contacts then ranks it first. Omit to keep the current one.
addedPostalAddressesNoPostal addresses to add.
removedPostalAddressesNoPostal addresses to remove, each given either as its `[a0]` handle or as its label (`home`, `work`).
updatedPostalAddressesNoCorrections to stored postal addresses: name the handle plus only the components that change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare only the safety profile (not read-only, not destructive, not idempotent), so the description must carry the mutation semantics — and it does: partial update with untouched fields preserved, `""` clearing behavior for all fields except name, note being fully replaced rather than appended, and preferredEmail affecting later search ranking. It adds real consequences an agent could not infer from annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core partial-update semantics and the alternative tool, then grouped by field family (scalars, add/remove lists, address corrections, preferredEmail). It is dense but a single long paragraph, and a few clauses repeat the schema's own field descriptions.

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

Completeness5/5

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

For a 15-parameter mutation tool with no output schema, the description supplies the missing glue: where ids and handles come from, how the added/removed/updated lists differ, clearing conventions, and the sibling to use for merges. Nothing an agent needs to invoke it correctly appears absent.

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 description coverage is 100%, so the baseline is 3; the description goes beyond it by explaining the add/remove/update list pattern, that removedPhones accepts either a handle or the raw number, and that a role is what the person is to the user and is later searchable. Some of the prose (naming the four scalar fields) merely restates what the schema already documents, keeping it short of a 5.

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?

States a specific verb and resource ("Edit a stored contact by id") plus the key scope constraint that only named fields change and everything else is preserved. It also names the sibling tools it is not (search_contacts for lookup, merge_contacts for deduplication), so an agent can place it without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing is given: use search_contacts to obtain contact_id and the `[a0]`-style handles, and use merge_contacts instead when two records are the same person. It also states a usage rule for roles (record only when the user said or confirmed, never inferred from mail), which prevents a common misuse.

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