Skip to main content
Glama

Update Contact

update_contact
Destructive

Update selected fields on an existing Microsoft 365 contact; only supplied fields change. For list fields, read the contact first and pass the complete replacement list because lists overwrite.

Instructions

Update fields on an existing contact. Only the fields passed are changed. List fields (email_addresses, business_phones, home_phones, categories) REPLACE the whole list — read the contact first and pass the complete new list; an empty list clears it.

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": {
      "contact_id": "<contact_id>"
    },
    "name": "update_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
surnameNoLast name
birthdayNoBirthday as YYYY-MM-DD, or an ISO 8601 timestamp (e.g. copied from another contact's birthday as-is)
nicknameNoNickname
job_titleNoJob title
categoriesNoComplete replacement list of Outlook categories
contact_idYesThe contact ID
given_nameNoFirst name
home_phonesNoComplete replacement list of home phones
company_nameNoCompany name
mobile_phoneNoMobile phone number
personal_notesNoReplaces the contact's notes
business_phonesNoComplete replacement list of business phones
email_addressesNoComplete replacement list of email addresses

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations flag destructiveHint=true, and the description explains exactly why: list fields are wholesale replacements, an empty list clears data, and callers must read-then-write. It also clarifies partial-update semantics ("only the fields passed are changed"), which the annotations alone do not convey.

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?

Three short sentences, front-loaded with purpose, then the partial-update rule, then the highest-risk caveat. No redundant or filler wording.

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?

Covers the risky semantics of a 13-parameter mutation tool well. With no output schema, it does not say what the update returns or whether it echoes the updated contact, which is a minor remaining gap.

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?

Schema coverage is 100%, so field meanings are already documented; the description still adds value by grouping the four list parameters and explaining replacement/clearing behavior as a rule rather than repeating per-field text. It does not cover the remaining scalar fields, but those are self-explanatory in the schema.

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 and resource ("Update fields on an existing contact"), and "existing" implicitly distinguishes it from create_contact/delete_contact. It stops short of naming a sibling alternative explicitly, so it is clear but not fully differentiated.

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 actionable workflow guidance — "read the contact first" — which effectively routes the agent through get_contact before mutating. It lacks an explicit when-not statement (e.g., use create_contact for new contacts), leaving that inference to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools