Skip to main content
Glama

updateContact

Idempotent

updateContact: Update an existing contact's information. Requires authentication. Only the fields you provide are changed; omitted fields keep their current values. Get the contactId from listContacts. Returns the updated contact. To make a contact usable as a .al registrant, send registryAttributes (see createContact).

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

Input Schema

NameRequiredDescriptionDefault
cityNoNew city name.
emailNoNew email address.
phoneNoNew phone number in '+CC.number' format, e.g. '+1.5551234567'.
stateNoNew state, province, or region.
countryNoNew country as a 2-letter ISO 3166-1 alpha-2 code, e.g. 'US'.
street1NoNew first street address line.
street2NoNew second street address line.
lastNameNoNew last name.
contactIdYesIdentifier of the contact to update, as returned by listContacts.
firstNameNoNew first name.
postalCodeNoNew postal or ZIP code.
sessionKeyNoSession key (osk_...) returned by checkDeviceLoginStatus. Pass it on every call when logged in via the in-chat device flow; omit when connected via OAuth.
organizationNoNew organization or company name.
registryAttributesNoRegistry-specific fields (.al / AKEP: entityType, doctype, docnr, nipt). REPLACES the whole stored set, so send every field, not just the changed one. Omit to keep the current ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / registryAttributes
      Added value: +{
      +  "description": "Registry-specific fields (.al / AKEP: entityType, doctype, docnr, nipt). REPLACES the whole stored set, so send every field, not just the changed one. Omit to keep the current ones.",
      +  "properties": {
      +    "docnr": {
      +      "type": "string"
      +    },
      +    "doctype": {
      +      "type": "string"
      +    },
      +    "entityType": {
      +      "type": "string"
      +    },
      +    "nipt": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed12 schema fields changed
    • addedInput schema / properties / city / description
      Added value: +"New city name."
    • addedInput schema / properties / contactId / description
      Added value: +"Identifier of the contact to update, as returned by listContacts."
    • addedInput schema / properties / country / description
      Added value: +"New country as a 2-letter ISO 3166-1 alpha-2 code, e.g. 'US'."
    • addedInput schema / properties / email / description
      Added value: +"New email address."
    • addedInput schema / properties / firstName / description
      Added value: +"New first name."
    • addedInput schema / properties / lastName / description
      Added value: +"New last name."
    • addedInput schema / properties / organization / description
      Added value: +"New organization or company name."
    • addedInput schema / properties / phone / description
      Added value: +"New phone number in '+CC.number' format, e.g. '+1.5551234567'."
    • addedInput schema / properties / postalCode / description
      Added value: +"New postal or ZIP code."
    • addedInput schema / properties / state / description
      Added value: +"New state, province, or region."
    • addedInput schema / properties / street1 / description
      Added value: +"New first street address line."
    • addedInput schema / properties / street2 / description
      Added value: +"New second street address line."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description adds meaningful behavioral detail: authentication is required, omitted fields retain current values, and the updated contact is returned. It also warns that registryAttributes is how to make a contact usable as a .al registrant, which is important context for a non-obvious field.

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?

The description is compact, front-loaded with the purpose, and each sentence carries useful information about authentication, partial updates, parameter sourcing, return behavior, or registry usage.

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 14-parameter mutation tool with a nested registryAttributes object and no output schema, the definition covers the essential behavioral context: authentication, update semantics, return value, and registry-specific usage. It could say more about error handling or the sessionKey flow, but the schema covers most field-level details.

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 coverage is 100%, so the schema already documents all parameters, including formats for phone, country, and registryAttributes replacement semantics. The description adds modest meaning by pointing to listContacts for contactId and createContact for registryAttributes, but most parameter-specific guidance is already in the schema.

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 description opens with a specific verb and resource: 'Update an existing contact's information.' It clearly distinguishes this from createContact, listContacts, and getContact by emphasizing updating an existing contact rather than creating, listing, or retrieving one.

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 explains that contactId comes from listContacts and points to createContact for registryAttributes context. It also states that only provided fields change, which guides partial updates. It does not explicitly say when to use createContact instead, but the update/create distinction is clear from the name and purpose.

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.