Skip to main content
Glama
Sign In
send16-mcp

send16-mcp

by spruikco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

remove_suppression

Remove an email from the suppression list after recipient confirmation to resume sending.

Instructions

Remove an email from the suppression list. Use only when you've confirmed the recipient wants to receive mail again.

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": "remove_suppression"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes
apiKeyNoSend16 API key (overrides SEND16_API_KEY env var)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.7

TDQS

A4/5.0
Behavior3/5

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

No annotations present, so description carries full burden. It states basic removal behavior but omits details like error handling, idempotency, or side effects.

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 concise sentences with no wasted words; front-loaded with action and usage condition.

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

Completeness3/5

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

For a simple suppression removal tool, description covers purpose and when-to-use but lacks details on return values, error states, or prerequisites.

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

Parameters2/5

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

Schema coverage is 50% (email has format/pattern, apiKey has description). Description adds no additional parameter context, failing to compensate for uncovered parts.

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 an email from the suppression list') and is distinct from sibling tools like add_suppression and list_suppressions.

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?

Explicitly says 'Use only when you've confirmed the recipient wants to receive mail again', providing clear when-to-use guidance.

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

Deploy Server

Other Tools