Skip to main content
Glama
Sign In
Ballast - Cold Email

Ballast - Cold Email

Official
by useballast
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

add_suppressions

Suppress up to 10,000 email addresses or whole domains per call to block leads from Ballast cold email campaigns. Matching leads are marked suppressed.

Instructions

Suppress addresses or whole domains Up to 10,000 values per call: emails, or domains written as @acme.com. Matching leads are marked suppressed.

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": {
      "values": "<values>"
    },
    "name": "add_suppressions"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: a 10,000-value per-call ceiling and the side effect that matching leads are marked suppressed. It omits permission requirements, reversibility, idempotency, and any note on partial failures within a large batch.

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?

Three short sentences, front-loaded with the core action and then the volume limit and accepted formats. Nothing is padded and the limits appear before the side-effect note.

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 two-parameter, no-output-schema tool the description is close to sufficient: it covers what gets suppressed and the batch limit. It falls short on the unexplained `reason` parameter and on what the caller should expect back, since no output schema exists to fill that gap.

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 0%, so the description must compensate. It fully explains the `values` parameter (emails or @domain format, up to 10,000), but the `reason` parameter is never mentioned, leaving one of two parameters undocumented in both the schema and the description.

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 (suppress) and specific resources (email addresses or whole domains), plus the accepted domain syntax. No sibling tool performs suppression, so the agent can distinguish it from add_leads_to_campaign or list_leads at a glance.

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?

The description never says when to reach for this tool versus alternatives, nor does it state prerequisites (e.g., whether suppression applies retroactively to existing campaigns or leads). Usage must be inferred entirely from the verb.

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