Skip to main content
Glama

remove_contact

DestructiveIdempotent

Remove a labeled contact from one or all chains. Specify the chain to delete only that entry, or omit to remove from every chain.

Instructions

Remove a labeled contact. Without chain, removes the label from EVERY chain that has it (one device interaction per chain when removing a signed entry). With chain, removes only that chain's entry — the label can survive on other chains. The unsigned metadata row (notes / tags) is dropped only when no chain still references the label. Issues CONTACTS_LABEL_NOT_FOUND if neither the signed disk nor the unsigned in-memory store has the label. Issue #428: unsigned-only removals never need a Ledger; mixed labels (signed entry on one chain + unsigned on another) require pairing only for the signed-entry chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesHuman-readable label, used to look up the contact by name in every prepare flow. Must be unique within a chain — adding the same label twice on the same chain replaces the address.
chainNoIf specified, removes the label from THAT chain only. If omitted, removes the label from EVERY chain that has it (one device interaction per chain).
Behavior5/5

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

Adds significant behavioral context: unsigned metadata retention, Ledger pairing requirements, and error conditions. Goes beyond annotations which already mark destructive and idempotent.

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?

Packed with information but front-loaded with the main action. Slightly verbose but every sentence adds value.

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?

Comprehensive coverage of behavior, edge cases (unsigned-only, mixed labels), and error conditions. No output schema but description is sufficient.

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 already fully describes parameters (100% coverage). Description adds nuanced behavior for chain parameter and clarifies removal across chains vs. single chain.

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?

Clearly states 'remove a labeled contact' and distinguishes behavior with and without the chain parameter. Differentiates from sibling tools like add_contact.

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

Usage Guidelines4/5

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

Explains when to use chain parameter vs. omit, and covers error condition. Could be improved by explicitly stating not to use when intending to edit rather than remove.

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/szhygulin/vaultpilot-mcp'

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