Skip to main content
Glama
Sign In
Precleared MCP Server

Precleared MCP Server

by gabrielaoimevbore-beep
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Opt-out list

suppress_contact
DestructiveIdempotent

Add an email address or whole domain to a key's opt-out list, or remove it, so later contact checks return blocked at no charge. Use it when someone unsubscribes or asks not to be contacted.

Instructions

Add an email address or a whole domain to this key's opt-out list, or remove it. Use it when someone unsubscribes, replies asking not to be contacted, or must never be emailed. Every later contact_check on a listed address answers blocked, free of charge, so the list works across every tool that uses the same key. Needs PRECLEARED_API_KEY: the list belongs to a key. Nothing is sent to the recipient.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "suppress_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe address to list. Give this or domain.
domainNoA whole domain to list, for example acme.co.uk. Give this or email.
reasonNoWhy, in a few words, for example 'replied asking not to be contacted'. Kept with the entry.
removeNoTrue to take the address or domain off the list instead. Default false.

Output Schema

NameRequiredDescriptionDefault
entryNoThe entry: id, type, masked_email, domain, reason, source, created_at.
chargedNoAlways false: listing is free.
createdNoTrue when a new entry was added; false when it was already listed.
removedNoTrue when an entry was removed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: it explains the key-wide blast radius of the list, the downstream effect that later contact_check calls answer blocked at no charge, the PRECLEARED_API_KEY auth prerequisite, and — importantly for a destructiveHint tool — that nothing is sent to the recipient. That last point removes a realistic false fear of emailing the person.

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?

The core action is front-loaded in the first clause, followed by use cases, then the benefit of suppression, then the auth requirement and the no-email reassurance. Every sentence carries distinct information with no repetition of schema or annotation fields.

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?

With annotations declaring destructive/idempotent behavior, a fully documented four-parameter schema, and an output schema handling return values, the description covers what remains: scope across tools, auth, cost, and the fact that no message goes out. Nothing an agent needs to call it safely is missing.

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 adds meaning by framing the tool as a two-way add-or-remove operation, which gives the `remove` flag context the schema alone only states mechanically. The `reason` field is left entirely to the schema, but that is a reasonable omission.

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 and resource — add an email address or whole domain to this key's opt-out list, or remove it — plus the scoping unit (the key). It is clearly distinguishable from contact_check, which it names as the downstream consumer, and from verify_receipt.

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

Usage Guidelines4/5

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

Gives concrete triggering situations: someone unsubscribes, replies asking not to be contacted, or must never be emailed. It doesn't explicitly say when to prefer contact_check over this tool or when not to suppress, but the usage context is clear enough to act on.

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