Skip to main content
Glama
agentisend

agentisend

Stop sending to an address

add_suppression
Idempotent

Blocks sending to an email address or entire domain so you can honor opt-out and do-not-contact requests immediately.

Instructions

Purpose: stop sending to an address, or to a whole domain (pass "@example.com"). Use it the moment someone asks not to be contacted. NOT for: undoing one (remove_suppression). Returns: the row that now blocks that address. Adding is always allowed and always safe; it is the direction that protects the account.

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": {
      "email": "<email>"
    },
    "name": "add_suppression"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe address to suppress, or "@example.com" for a whole domain.
levelNoDefaults to address, or domain when the value starts with @.
originNoWhy the address is blocked. Defaults to manual.
idempotency_keyNoYour own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect.

Output Schema

NameRequiredDescriptionDefault
idNoIdentifier.
emailNo
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
levelNo
originNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, so the safety profile is partly covered. The description adds genuine value by asserting 'Adding is always allowed and always safe; it is the direction that protects the account,' clarifying that this mutation is non-destructive and unrestricted. It stops short of noting rate limits or that it affects future sends only.

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?

Labeled sections (Purpose / NOT for / Returns) front-load the essential information and read efficiently with no filler. The 'Returns:' line is largely redundant given a dedicated output schema exists, so it doesn't fully earn its place.

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?

Because an output schema exists, the description needn't detail return shape, and annotations plus schema cover the safety and parameter surface. The description completes the picture with purpose, routing to the sibling inverse, and safety reassurance — nothing an agent needs to call this correctly is missing.

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%, and the enum values, defaults, and idempotency semantics are all fully documented in the schema. The description merely restates the '@example.com' domain syntax already present in the email parameter, adding no meaning beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource ('stop sending to an address, or to a whole domain') and explicitly distinguishes itself from the sibling remove_suppression by naming the inverse operation. An agent can select this over list_suppressions or remove_suppression without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger condition ('Use it the moment someone asks not to be contacted') and an explicit exclusion with the alternative named ('NOT for: undoing one (remove_suppression)'). This is textbook when/when-not/alternative guidance.

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