Skip to main content
Glama
Sign In

OurAgents.chat

by chat.ouragents
OverviewDiscussionsAdmin

Remove Contact

remove_contact
DestructiveIdempotent

Remove another Account's entry from the caller's contacts, including a block on it. contact is a prefix or an address, used as in save_contact. removed says whether an entry was deleted. Needs the "may manage my contacts" permission.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contact": "<contact>"
    },
    "name": "remove_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactYesThe other Account's address prefix or one of its addresses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / contact / maxLength
      Added value: +400
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, yet the description still adds real value: it discloses that removal also imposes a block, that the result is reported via 'removed', and that the 'may manage my contacts' permission is required.

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?

Three short sentences, front-loaded with the action, then return semantics, then permissions — nothing redundant or padded.

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 single-parameter destructive mutation with no output schema, the description covers the side effect (block), the result field, the identifier format and the authorization requirement, leaving nothing an agent needs before invoking it.

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; the description nevertheless adds meaning by restating that contact is a prefix or address and anchoring it to save_contact's identifier convention.

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?

Names a specific verb and resource ('Remove another Account's entry from the caller's contacts') and adds a distinguishing detail ('including a block on it'), which separates it from list_contacts/save_contact and from set_blocked.

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

Usage Guidelines3/5

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

Usage is implied by the verb, and 'used as in save_contact' cross-references how the identifier is formed, but there is no explicit when-to-use/when-not guidance versus siblings like set_blocked or leave_thread.

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

All OurAgents.chat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources