Skip to main content
Glama

graph_delete_contact

Delete a specified Outlook contact by its contact ID to remove it from Microsoft Graph when no longer needed.

Instructions

Delete an Outlook contact.

Args: contact_id: The contact ID to delete.

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_delete_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about whether deletion is permanent or recoverable, what permissions are required, or what happens if contact_id does not exist. For a destructive mutation with zero annotation coverage, that is a meaningful gap; only the implicit destructiveness of "Delete" is conveyed.

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?

The definition is one sentence plus a single arg line, front-loaded with the action and free of filler. The docstring-style "Args:" block is slightly mechanical but not wasteful.

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?

The tool is simple (one required string parameter, no output schema), so a short description is defensible. However, as a destructive operation with no annotations and no parameter documentation, it omits irreversibility and failure behavior that an agent would need before invoking it.

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

Parameters2/5

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

Schema description coverage is 0% for the single parameter, so the description must compensate. "The contact ID to delete" merely restates the parameter name and adds no format, source (e.g., from graph_list_contacts), or validity information beyond what the schema already shows.

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?

The description states a specific verb and resource ("Delete an Outlook contact"), which is unambiguous and clearly distinct from siblings such as graph_update_contact or graph_delete_event. It stops short of naming an alternative or clarifying scope (personal vs. shared contacts), so it is clear but not sibling-differentiating beyond the resource noun.

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 when-to-use guidance, no mention of preconditions such as owning the contact or confirming intent, and no reference to any alternative tool. The agent must infer everything about when this call is appropriate from the single verb.

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