Skip to main content
Glama

Delete Contact

delete_contact
Destructive

Remove a duplicate contact from Microsoft 365 after copying its missing emails, phones, notes, or birthday to the kept contact. Returns the deleted contact's details so they aren't lost.

Instructions

Delete a contact. Intended for duplicates: first copy anything the duplicate holds that the kept contact lacks (emails, phones, notes, birthday) onto the kept contact with update_contact, then delete. Returns the deleted contact's details so they are not lost from the conversation.

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

Input Schema

NameRequiredDescriptionDefault
contact_idYesThe contact ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is structured. The description adds real value beyond that: the data-loss mitigation workflow and the fact that the deleted contact's details are returned so the agent can retain them in conversation. It doesn't state whether deletion is permanent or recoverable, which keeps it at 4.

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

Conciseness4/5

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

Three sentences, front-loaded with the action, then the operating procedure, then the return behavior. Every sentence carries information, though the middle sentence is dense and could be split for readability.

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

Completeness5/5

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

For a single-parameter destructive tool with no output schema, the description covers purpose, required pre-workflow, and what comes back. An agent has everything it needs to invoke this safely without guessing.

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?

There is a single required parameter (contact_id) with 100% schema description coverage, so the schema already carries the semantics. The description adds nothing about the parameter, and the high coverage baseline of 3 applies.

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: 'Delete a contact', and narrows intent to duplicate cleanup. It does not fully differentiate from other deletion siblings (delete_draft, delete_event, etc.), but the resource noun makes the target unambiguous.

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 an explicit when-to-use case ('Intended for duplicates') plus a concrete pre-step order: copy missing fields onto the kept contact with update_contact, then delete. It lacks an explicit when-not-to-use case (e.g., deleting a contact that has no duplicate), so it falls short of a 5.

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