Skip to main content
Glama

Change a contact

contact_update
DestructiveIdempotent

Changes one contact's name, company, designation, notes or labels. Only the fields passed change; labels, if passed, replace the contact's labels. Phone numbers and emails cannot be changed here. Never deletes.

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": "contact_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
notesNo
dryRunNoIf true, return what would change without saving
labelsNoReplaces the contact's labels
companyNo
lastNameNo
contactIdYesThe contact's id
firstNameNo
designationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / contactId / description
      Previous value: -"The contact id from contact_list, contact_search or contact_by_phone"New value: +"The contact's id"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Discloses genuinely non-obvious behavior beyond the annotations: only passed fields change (partial update), and passed labels replace the existing label set entirely. It also clarifies no deletion of the contact occurs. The 'Never deletes' phrasing sits in mild tension with destructiveHint=true, but is consistent with the label-replacement caveat rather than a contradiction; no permission or rate-limit context is given.

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?

Four short sentences, front-loaded with the mutable field list, followed by the partial-update rule and then the two hard constraints. Every sentence carries distinct information with no padding.

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?

Covers mutable fields and the label-replacement hazard well, and there is no output schema to explain. But for a 9-parameter mutation tool at 33% schema coverage, leaving contactId, firstName/lastName versus name, and dryRun unaddressed leaves the definition short of complete.

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

Parameters3/5

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

With schema coverage at 33% across 9 parameters, the description must carry weight and it partially does: it explains label replacement semantics and that omitted fields are untouched. However it omits the required contactId, does not clarify the relationship between 'name' and the separate firstName/lastName parameters, and never mentions dryRun beyond what the schema says.

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?

States a specific verb (changes) and resource (one contact) and enumerates the mutable fields: name, company, designation, notes, labels. The scope is clear enough to separate it from contact_create or lead_update, though it never names a sibling explicitly.

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?

Gives real routing signal with the exclusion 'Phone numbers and emails cannot be changed here,' telling the agent when this tool will not work. It lacks a pointer to which sibling handles phones/emails and no explicit when-to-use-vs-alternative comparison is offered.

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.