Skip to main content
Glama

remove_contact

Remove a contact from the local signal-cli contact list. This only deletes the local record; it does not block the contact or affect message history.

Instructions

Remove a contact from the local signal-cli contact list on this device. This only removes the local record — it does NOT block the contact, delete message history, or affect the contact's ability to message you. To prevent incoming messages, use block_contact instead. Use update_contact to set a local display name without removing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesPhone number to remove (E.164 format)

Implementation Reference

  • Schema definition for the remove_contact tool, which requires a 'number' parameter in E.164 format and describes it as a local-only removal.
    Tool(
        name="remove_contact",
        description=(
            "Remove a contact from the local signal-cli contact list on this device. "
            "This only removes the local record — it does NOT block the contact, delete message history, "
            "or affect the contact's ability to message you. "
            "To prevent incoming messages, use block_contact instead. "
            "Use update_contact to set a local display name without removing."
        ),
        inputSchema={
            "type": "object",
            "properties": {
                "number": {"type": "string", "description": "Phone number to remove (E.164 format)"},
            },
            "required": ["number"],
        },
    ),
  • Registration of remove_contact's required parameter 'number' in the _REQUIRED validation dict.
    "remove_contact":       ["number"],
  • Handler for remove_contact in the call_tool dispatcher — calls client.remove_contact() and returns a success response.
    elif name == "remove_contact":
        await client.remove_contact(arguments["number"])
        return _ok({"status": "removed", "number": arguments["number"]})
  • Client helper that executes the actual JSON-RPC call to signal-cli with method 'removeContact' and the recipient number parameter.
    async def remove_contact(self, number: str) -> None:
        await self._rpc("removeContact", {"recipient": number})
Behavior5/5

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

With no annotations, the description bears the full burden and it delivers: it states what the tool does (removes local record) and explicitly what it does NOT do (block, delete history, affect messaging). This covers behavioral implications comprehensively.

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?

The description is concise: two sentences that first state the action, then clarify scope and exclusions, and finally provide alternative tools. Every sentence adds value without redundancy.

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 simple tool with one parameter and no output schema, the description is fully complete. It covers purpose, scope, behavioral implications, and usage alternatives, leaving no significant gaps.

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 coverage is 100% for the single parameter 'number', which already has a clear description. The tool description does not add additional semantic context beyond the schema, so baseline score of 3 is appropriate.

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?

The description clearly states the action ('Remove a contact from the local signal-cli contact list') and the resource ('local record'). It distinguishes from siblings by explicitly mentioning block_contact and update_contact, making the purpose unambiguous.

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?

The description provides explicit guidance on when to use this tool versus alternatives: 'To prevent incoming messages, use block_contact instead. Use update_contact to set a local display name without removing.' This fully satisfies the guideline criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googlarz/signal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server