Skip to main content
Glama

HonestCRM

Update a contact

update_contact
DestructiveIdempotent

Change fields of a contact. Send only the fields to change.

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
idYesThe id of the contact.
titleNoJob title, such as Head of Sales.
customNoCustom field values as an object of custom field id to value.
emailsNoEmail addresses. The first one is the primary address.
phonesNoPhone numbers. The first one is the primary number.
lastNameNoLast name.
companyIdNoThe id of the company the contact works for. Use search to find it.
firstNameNoFirst name.
ownerUserIdNoThe id of the user who owns the contact. Default: the signed-in user.
leadSourceIdNoThe id of the lead source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and idempotentHint=true; the description adds meaningful PATCH-style semantics by telling the agent that omitted fields are left alone, which is not derivable from the schema. It stops short of the hazard most relevant to a destructive update: that 'emails'/'phones' arrays and 'custom' are wholesale replaced rather than merged, and that passing null clears nullable fields.

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?

Two short sentences with zero padding; the core action is front-loaded and the calling convention follows immediately. It is lean to the point of omitting important detail, but nothing present is wasted.

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

Completeness2/5

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

For a 10-parameter destructive mutation with a nested object and no output schema, the description is thin: it omits array-replacement and null-clearing semantics, what a successful response looks like at a high level, and any error/permission behavior. The annotations cover the safety profile, but the destructive specifics an agent most needs are missing.

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?

Schema description coverage is 100%, so every parameter is already documented, including the companyId hint to use search. The description's partial-update rule adds non-trivial meaning the schema cannot express (omitted fields are untouched), which lifts it just above the baseline, but it says nothing about the nested 'custom' object or array replacement ordering.

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 ('Change fields of a contact'), which clearly separates it from create_contact and get_contact. It does not explicitly name a sibling tool, but the update semantics are unambiguous.

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?

'Send only the fields to change' establishes partial-update usage, which is useful guidance about how to call it. However, it gives no when-to-use vs. when-not guidance, no mention of prerequisites (e.g., resolving companyId/ownerUserId via search), and no exclusion pointing agents elsewhere.

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.

Resources