Skip to main content
Glama
googlarz

Signal MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_contact

DestructiveIdempotent

Delete a contact entry (name, nickname, note) from your Signal contact list. Optionally hide it or permanently forget all data; this does not block the contact.

Instructions

Delete a contact's entry (name, nickname, note) from your contact list; synced to your linked devices. It does not block them, delete messages or stop them messaging you — use block_contact for that. number (required, E.164). hide (default false): only hide the contact from the list and keep its data. forget (default false): delete ALL data for this recipient, including identity keys and sessions — not reversible. hide and forget are mutually exclusive (error if both). Returns status 'removed' and number. To rename instead, use update_contact.

Input Schema

NameRequiredDescriptionDefault
hideNoHide the contact but keep its data
forgetNoDelete all data for this recipient, including identity keys and sessions
numberYesPhone number to remove (E.164 format)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.40.1
    • addedInput schema / properties / forget
      Added value: +{
+  "default": false,
+  "description": "Delete all data for this recipient, including identity keys and sessions",
+  "type": "boolean"
+}
    • addedInput schema / properties / hide
      Added value: +{
+  "default": false,
+  "description": "Hide the contact but keep its data",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / number / description
      Previous value: -"Phone number to remove"New value: +"Phone number to remove (E.164 format)"
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description goes further: it discloses that changes sync to linked devices, that forget is irreversible and wipes identity keys and sessions, that hide/forget are mutually exclusive with an error on conflict, and that the result status is 'removed'. That is substantial behavior beyond the annotations.

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?

Dense but front-loaded: the core action and its scope boundaries come first, then parameter caveats and the result shape. Every sentence adds an actionable fact (alternatives, irreversibility, exclusivity, return value) without filler.

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?

Despite having no output schema, the description states what is returned ('status removed' and number), covers the destructiveness and irreversibility of forget, and routes to sibling tools. Nothing an agent needs to call this safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it clarifies that hide keeps data versus forget deleting ALL data, and it documents the mutual-exclusivity constraint and error behavior that the schema does not express. It stops short of five only because the core per-parameter semantics largely duplicate the schema.

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

Purpose5/5

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

States a specific verb (Delete) and resource (a contact's entry) and immediately delimits scope by saying it does not block, delete messages, or stop messaging. This clearly distinguishes it from siblings block_contact and update_contact without opening their schemas.

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

Usage Guidelines5/5

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

Explicitly names when-not to use it ('use block_contact for that') and names the alternative for a related operation ('To rename instead, use update_contact'). Both exclusion and redirect are stated rather than implied.

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