Skip to main content
Glama

t2000_contact_remove

Remove a saved contact by name from the t2000 MCP server's banking system.

Instructions

Remove a saved contact by name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesContact name to remove

Implementation Reference

  • Registration and handler implementation for the t2000_contact_remove tool.
    server.tool(
      't2000_contact_remove',
      'Remove a saved contact by name.',
      {
        name: z.string().describe('Contact name to remove'),
      },
      async ({ name }) => {
        try {
          const removed = agent.contacts.remove(name);
          return { content: [{ type: 'text', text: JSON.stringify({ success: removed, name }) }] };
        } catch (err) {
          return errorResult(err);
        }
      },
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the tool removes a contact, implying a destructive mutation, but doesn't disclose critical details like whether removal is permanent, requires specific permissions, has side effects, or what happens on success/failure. This leaves significant gaps for safe agent invocation.

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 a single, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse, though this conciseness comes at the cost of completeness in other dimensions.

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 tool's destructive nature (implied by 'Remove'), lack of annotations, and no output schema, the description is insufficient. It doesn't cover behavioral risks, response format, error conditions, or dependencies, leaving the agent with inadequate context for reliable use in a complex server environment with many siblings.

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 description coverage is 100%, with the parameter 'name' clearly documented in the schema as 'Contact name to remove'. The description adds no additional semantic context beyond what's in the schema, such as format examples or uniqueness constraints, so it meets the baseline for high schema coverage.

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?

The description clearly states the action ('Remove') and target resource ('a saved contact by name'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 't2000_contact_add' or 't2000_contacts' beyond the obvious verb difference, missing an opportunity to clarify scope or relationship.

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. The description doesn't mention prerequisites (e.g., contact must exist), exclusions, or how it relates to sibling tools like 't2000_contacts' (which might list contacts) or 't2000_contact_add' (which adds them).

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/mission69b/t2000'

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