Skip to main content
Glama

update_contact

Modify contact details in Microsoft MCP by specifying contact ID, account ID, and desired updates, ensuring accurate and current contact records.

Instructions

Update contact information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
contact_idYes
updatesYes

Implementation Reference

  • The handler function for the 'update_contact' MCP tool. It performs a PATCH request to the Microsoft Graph API endpoint /me/contacts/{contact_id} with the provided updates dictionary, returning the result or a status message.
    @mcp.tool
    def update_contact(
        contact_id: str, updates: dict[str, Any], account_id: str
    ) -> dict[str, Any]:
        """Update contact information"""
        result = graph.request(
            "PATCH", f"/me/contacts/{contact_id}", account_id, json=updates
        )
        return result or {"status": "updated"}
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. It doesn't indicate whether this is a read-only or destructive operation, what permissions are required, whether changes are reversible, what happens on success/failure, or any rate limits. For a mutation tool with zero annotation coverage, this lack of behavioral information is critically inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (3 words) but this brevity comes at the cost of being under-specified rather than efficient. While it's front-loaded with the core action, it lacks the necessary detail that would make it genuinely helpful. The structure is minimal but not effectively informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with 3 parameters, no annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It doesn't explain what the tool does beyond the name, provides no behavioral context, offers no parameter guidance, and gives no indication of what to expect from the operation. This leaves the agent with insufficient information to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and 3 parameters (account_id, contact_id, updates), the description provides zero information about any parameters. It doesn't explain what 'updates' should contain, what format the IDs require, or how these parameters interact. The description fails to compensate for the complete lack of schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update contact information' is a tautology that essentially restates the tool name 'update_contact'. While it identifies the resource ('contact information'), it lacks specificity about what aspects can be updated or how this differs from sibling tools like 'create_contact' or 'delete_contact'. The description doesn't provide a clear, distinct purpose beyond the obvious.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing contact), when not to use it (e.g., for creating new contacts), or how it relates to sibling tools like 'create_contact', 'delete_contact', or 'get_contact'. There's complete absence of contextual usage information.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elyxlz/microsoft-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server