Skip to main content
Glama
Sign In
send16-mcp

send16-mcp

by spruikco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

add_suppression

Add an email address to the suppression list to block future email deliveries.

Instructions

Add an email to the suppression list. Future sends to this address will be blocked.

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
emailYes
notesNo
apiKeyNoSend16 API key (overrides SEND16_API_KEY env var)
reasonNomanual

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.7

TDQS

B3.3/5.0
Behavior3/5

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

Discloses the effect of blocking future sends, but lacks details on reversibility, permanence, or required permissions. Since no annotations are provided, the description carries the full burden and is only partially sufficient.

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?

Extremely concise: two sentences with no wasted words. Information is front-loaded.

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 4 parameters, no output schema, and no annotations, the description omits critical context: what happens if the email is already suppressed, how to specify a reason, and whether this is reversible. The tool's behavior is under-specified.

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 low (25%). The description does not explain the 'notes' or 'reason' parameters, leaving their purpose implicit. Only the email's role is inferred from context.

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 verb ('Add'), resource ('suppression list'), and outcome ('Future sends...blocked'). It distinguishes from siblings like 'remove_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 Guidelines2/5

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

No guidance on when to use this tool vs alternatives (e.g., remove_suppression, list_suppressions). No mention of prerequisites or exclusions.

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