Skip to main content
Glama

Delete contact

delete_contact
Destructive

Delete a personal Outlook contact by ID, moving it to Deleted Items by default or permanently removing it when requested.

Instructions

Delete a personal contact (moved to Deleted Items unless permanent).

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": {
      "id": "<id>"
    },
    "name": "delete_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesContact ID
permanentNoPermanently delete (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 safety profile is known. The description adds genuinely new behavioral context beyond that: the default operation only moves the contact to Deleted Items and is therefore recoverable, while permanent deletion is a separate mode. It does not describe authorization requirements or what is returned.

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?

A single short sentence with the core action front-loaded and the conditional behavior condensed into a parenthetical. Nothing is wasted and nothing needs reordering.

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 two-parameter destructive tool whose annotations already flag destructiveness, the description covers the essential recoverability distinction an agent needs before calling. Minor gaps remain around permissions and post-call response, but the tool's low complexity means these are not blocking.

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 description coverage is 100%, so both parameters (id, permanent) are already documented, making 3 the baseline. The parenthetical restates the effect of non-permanent deletion, which loosely complements the permanent parameter, but it adds no format, constraint, or edge-case detail beyond 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 ("Delete a personal contact") and adds the key semantic that deletion is soft by default. It is clearly distinguishable from siblings such as delete_event or delete_folder by naming the resource type, though it does not explicitly contrast with them.

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

Usage Guidelines3/5

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

The purpose implies when to use it (removing a contact), and the parenthetical hints that callers should consider whether they want a recoverable or permanent removal. There is no explicit when-not guidance, no mention of prerequisites or required permissions, and no routing to alternatives like update_contact.

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