Skip to main content
Glama

Delete contact

delete_contact
DestructiveIdempotent

Delete a contact. Its conversations and their messages go with it and cannot be restored. A contact who is online right now, or who is on an AI phone call, cannot be deleted.

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_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 idempotentHint=true; the description earns credit by adding what those hints cannot: the cascade to conversations and messages and the fact that it cannot be restored. It also discloses the two blocking states (online, on an AI phone call), a genuine behavioral condition. It stops short of saying how failure surfaces (error vs. silent no-op) or what permissions are required.

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?

Three short sentences, front-loaded with the action, then the destructive consequence, then the failure conditions. Nothing is redundant and the riskiest information is placed prominently.

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 one-parameter destructive tool with no output schema, the description covers the main things an agent needs: what is destroyed, irreversibility, and when the call is blocked. The remaining gaps, failure mode and permission requirements, are minor and partly covered by the destructiveHint annotation.

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?

The single parameter contact_id has 0% schema description coverage, but the name is self-describing as an integer identifier. The description adds no detail about its meaning, scope, or accepted values beyond that, so it neither compensates for nor worsens the coverage gap.

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?

"Delete a contact" states a specific verb and resource, and the follow-up sentence scopes the blast radius to the contact's conversations and messages. It is clearly distinguishable from the delete_* siblings by resource, though it never explicitly names another tool as the alternative for a given situation.

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 description supplies preconditions rather than selection guidance: a contact who is online or on an AI phone call cannot be deleted, which tells the agent when the call will fail. There is no explicit statement of when to delete vs. deactivate/update instead, so usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources