Skip to main content
Glama

Update contact

update_contact
Destructive

Update a contact. Only the inputs you pass change; tags and fields replace the whole list or map.

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
nameNoDisplay name. Null clears it
tagsNoLabels that group contacts
emailNoEmail address. Null clears it
notesNoFree-text notes. Null clears them
stateNoUS state or Canadian province, usually a 2-letter code. Null clears it
fieldsNoUp to 20 string values
sourceNoWhere the contact came from. Null clears it
companyNoCompany name. Null clears it
last_nameNoLast name. Null clears it
first_nameNoFirst name. Null clears it
phone_numberNoE.164, US or Canada

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / company / description
      Added value: +"Company name. Null clears it"
    • addedInput schema / properties / email / description
      Added value: +"Email address. Null clears it"
    • addedInput schema / properties / first_name / description
      Added value: +"First name. Null clears it"
    • addedInput schema / properties / last_name / description
      Added value: +"Last name. Null clears it"
    • addedInput schema / properties / name / description
      Added value: +"Display name. Null clears it"
    • addedInput schema / properties / notes / description
      Added value: +"Free-text notes. Null clears them"
    • addedInput schema / properties / source / description
      Added value: +"Where the contact came from. Null clears it"
    • addedInput schema / properties / state / description
      Added value: +"US state or Canadian province, usually a 2-letter code. Null clears it"
    • addedInput schema / properties / tags / description
      Added value: +"Labels that group contacts"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds the genuinely non-obvious semantics: unspecified inputs are left alone, while tags and fields are wholesale replacements. That replacement clause goes a long way toward explaining the destructive hint. It still doesn't state what happens to the replaced tags/fields or whether clearing via null is recoverable.

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, no filler, and the more surprising fact (replace-vs-patch semantics for tags/fields) is placed second where it lands as a caveat rather than being buried. Every clause carries information.

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?

For a 12-parameter mutation tool with rich schema docs and no output schema, the description covers the subtle partial-update behavior that would otherwise cause accidental data loss. It is slightly incomplete in not routing the agent away from upsert_contact or bulk_update_contacts, but the core semantics are sound.

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 per-parameter meaning is already fully documented, including the "Null clears it" convention and max lengths. The description goes beyond the schema by explaining cross-parameter behavior — partial updates versus whole-collection replacement for tags/fields — which the schema cannot express.

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?

"Update a contact" is a specific verb+resource, so the agent knows exactly which entity is being mutated. However, it never distinguishes this tool from near neighbors like upsert_contact or bulk_update_contacts, which is the only thing separating a 4 from a 5 here.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance and never mentions the obvious alternatives (upsert_contact for create-or-update, bulk_update_contacts for multiple records, update_customer for the parent entity). The partial-update semantics implies a use case but does not exclude any.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.