Skip to main content
Glama

update_contact_profile

Edit a contact's name, email, phone, company or address using the current contact revision. Omitted fields keep their saved values.

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>",
      "revision": "<revision>",
      "requestId": "<requestId>",
      "profile": "<profile>"
    },
    "name": "update_contact_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
profileYes
revisionYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, so the safety profile is covered. The description usefully adds partial-update semantics ('omitted fields keep their saved values'), which matters given idempotentHint=false, but it says nothing about what happens on a revision mismatch or what the requestId is for. Adds real value without disclosing failure behavior.

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, zero filler, with the field list and the partial-update rule front-loaded. Nothing could be removed without losing meaning.

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 a 4-required-parameter mutation with a nested object, no output schema, and no schema descriptions, the definition covers scope and update semantics but omits concurrency-failure behavior and the purpose of requestId. Adequate but incomplete for the complexity.

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 0%, so the description must carry parameter meaning. It enumerates the profile sub-fields that match the nested object and explains that revision is the 'current' one, but leaves id and especially requestId (a UUID with no explanation, likely an idempotency key) completely undocumented.

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 (Edit) and resource (contact profile) plus the exact updatable fields, so it is clearly distinguishable from create_contact or add_contact_tag. It stops short of naming a sibling alternative, so it lands at 4 rather than 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: 'using the current contact revision' hints that the caller must hold a fresh revision, but there is no explicit when-to-use, when-not-to-use, or guidance on what to do when the revision is stale. An agent must infer the precondition.

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