Skip to main content
Glama

update_my_contact

Update the coach's own contact info (confirm-gated). Sends the full object — fields omitted are cleared, so read get_my_profile first if only changing one field.

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": {
      "phone": "<phone>",
      "addressLine1": "<addressLine1>",
      "city": "<city>",
      "country": "<country>"
    },
    "name": "update_my_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYes
phoneYes
stateNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
countryYes
postalCodeNo
addressLine1Yes
addressLine2No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the mutation annotations, it discloses the crucial full-object replacement behavior and warns that omitted fields are cleared. The confirm-gated wording also signals guarded execution, providing substantial safety context without contradicting the annotations.

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 compact sentences front-load the purpose and then convey the replacement semantics, data-clearing risk, and read-first workflow. There is no filler or redundant explanation.

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 flat eight-parameter mutation, it supplies the scope, prerequisite read, confirmation requirement, and data-clearing behavior needed for a safe call. A minor gap is that preview-versus-execute behavior is left to the confirm parameter's schema, and no response behavior is summarized despite the absence of an output schema.

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?

With only 13% schema description coverage, the description meaningfully compensates by explaining cross-parameter replacement and omission semantics, plus the confirmation gate. It does not add formats or validation guidance for the individual phone and address values.

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?

The specific verb and resource—updating the coach's own contact info—make the tool's purpose immediately clear. The ownership scope distinguishes it from update_client_contact_details, while the contact-info resource distinguishes it from the other update_my siblings.

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?

It gives concrete guidance for the common partial-update case: read get_my_profile first if only one field is changing. The coach's-own scope implies when to select it, but it does not explicitly name the client-contact alternative or state other when-not conditions.

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.