Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

Delete Recipients

delete_recipients
DestructiveIdempotent

Permanently delete recipients: removes each from all groups, and deletes all emails for those addresses (both historical and queued). Addresses not in the database are ignored.

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": {
      "Recipients": "<Recipients>"
    },
    "name": "delete_recipients"
  }
}

Input Schema

NameRequiredDescriptionDefault
RecipientsYesRecipient email addresses to delete.

Output Schema

NameRequiredDescriptionDefault
ResultYesResult of the operation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, but the description goes beyond them by spelling out exactly what is destroyed (group memberships, historical and queued emails) and that unknown addresses are silently ignored rather than erroring. It still omits permission requirements or whether deletion is reversible/recoverable, keeping it short of a 5.

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?

Two tight sentences: the destructive scope comes first, the no-op carve-out second. Nothing is redundant with the title or schema, and no sentence could be dropped without losing information.

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

Completeness4/5

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

For a destructive single-parameter tool with a full annotation set and an output schema, the description covers what an agent most needs: what gets destroyed and how unknown inputs are handled. Only ancillary details like permission requirements or the 1000-address batch cap (already in the schema) are absent.

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?

With 100% schema coverage the baseline is 3, but the description adds real semantic content about the Recipients array: entries not present in the database are ignored rather than failing the batch. That changes how an agent should construct and interpret the call.

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 gives a specific verb and resource ('Permanently delete recipients') and immediately enumerates the cascade scope: removal from all groups and deletion of all emails, historical and queued. That scope detail makes it unambiguously distinct from edit_recipient or remove_group_members.

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?

It states behavior but never says when to reach for this tool versus alternatives such as remove_group_members (group-only removal) or edit_recipient. There are no prerequisites or exclusions, so an agent must infer the choice from the name alone.

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

All GoodSender 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