Skip to main content
Glama

graph_update_contact

Updates an Outlook contact by changing only the fields you supply, such as name, email, phone, company, or job title.

Instructions

Update an Outlook contact. Only the supplied fields are changed.

Args: contact_id: The contact ID to update. given_name: New first name. surname: New last name. email: New primary email address. mobile_phone: New mobile phone number. company_name: New company name. job_title: New job title.

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

Input Schema

NameRequiredDescriptionDefault
emailNo
surnameNo
job_titleNo
contact_idYes
given_nameNo
company_nameNo
mobile_phoneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose one meaningful trait beyond the schema: unspecified fields are left untouched rather than nulled. It says nothing about permissions, behavior when contact_id does not exist, or what happens to a field when an empty string is passed despite the empty-string defaults in the schema.

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 purpose and the partial-update rule are front-loaded in two sentences, followed by a compact Args list that earns its space given the 0% schema coverage. No filler or redundant restatement of the tool name.

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 seven-parameter mutation tool with no annotations and no output schema, the description covers the field list and mutation semantics adequately. It is still missing the empty-string/clearing behavior, existence and permission requirements, and any mention of the result, which matter for a destructive-by-nature operation.

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 description coverage is 0%, so the description must compensate, and it does: all seven parameters are named with a plain-language meaning ("New primary email address," "New job title"), which the schema provides only as bare property names. The gap is the unaddressed interaction between the "" defaults and the claim that only supplied fields change, leaving ambiguity about whether an empty string clears a field.

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?

"Update an Outlook contact" gives a specific verb and resource, and the second sentence narrows it to a partial update rather than a full replacement. It is clearly distinct from graph_create_contact and graph_delete_contact by verb alone, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to reach for this tool versus graph_create_contact or graph_delete_contact, and no prerequisites such as required scopes or the need for the contact to already exist. The only usage-relevant signal is the implied patch semantics from "Only the supplied fields are changed."

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