Skip to main content
Glama

remove_contact

Remove a provider from the active agent's contacts list using their npub identifier.

Instructions

Remove a provider from the active agent's contacts list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
npubYes

Implementation Reference

  • The actual handler function for the remove_contact tool. Decodes the npub, calls removeContact from storage, and returns success or not-found message.
    async handler(ctx, input) {
      ctx.toolRateLimiter.check();
      checkLen('npub', input.npub, MAX_NPUB_LEN);
    
      const agent = ctx.active();
      if (!agent.agentDir) {
        return errorResult('Active agent is ephemeral; nothing to remove.');
      }
    
      let pubkey: string;
      try {
        pubkey = decodeNpub(input.npub);
      } catch (e) {
        return errorResult(`Invalid npub: ${e instanceof Error ? e.message : String(e)}`);
      }
    
      const removed = await removeContact(agent.agentDir, pubkey);
      return removed
        ? textResult(`Removed contact ${input.npub}.`)
        : textResult(`No contact found for ${input.npub}.`);
    },
  • Zod schema for remove_contact input: expects a single 'npub' string field (min 1, max MAX_NPUB_LEN).
    const RemoveContactSchema = z.object({
      npub: z.string().min(1).max(MAX_NPUB_LEN),
    });
  • Registration of remove_contact as a ToolDefinition with name 'remove_contact', description, schema, and handler.
    defineTool({
      name: 'remove_contact',
      description: "Remove a provider from the active agent's contacts list.",
      schema: RemoveContactSchema,
  • The removeContact storage helper function that reads .contacts.json, filters out the contact by pubkey, and writes the file atomically. Returns true if a contact was removed.
    export async function removeContact(agentDir: string, pubkey: string): Promise<boolean> {
      const path = pathFor(agentDir);
      return withLock(path, async () => {
        const data = await readRaw(path);
        const before = data.contacts.length;
        data.contacts = data.contacts.filter((existing) => existing.pubkey !== pubkey);
        if (data.contacts.length === before) {
          return false;
        }
        await writeRaw(path, data);
        return true;
      });
    }
Behavior2/5

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

The description does not disclose behavioral traits beyond the basic action, e.g., what happens if the npub is invalid or if the contact is not found. No annotations are provided.

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 description is a single concise sentence with no unnecessary information, though it could be slightly expanded without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple tool, the description lacks details on return values, error handling, and prerequisites, making it incomplete for safe invocation.

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

Parameters1/5

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

Schema coverage is 0% and the description does not explain the 'npub' parameter's meaning or format, leaving the agent without semantic context.

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' and the resource 'a provider from the active agent's contacts list,' distinguishing it from sibling '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 Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as whether the contact must exist or any prerequisites.

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/elisymlabs/elisym'

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