Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp
OverviewDiscussionsAdmin

send_code

Queue an assigned code to the participant who holds it, by email, SMS or both. SENDS A REAL MESSAGE — it leaves the platform and cannot be recalled. There is no address field: the recipient is whoever holds the code. confirm=true is REQUIRED; set it only after the user approved sending to that specific participant. both sends on each channel the participant has a usable address for. Account suppressions and rate limits are enforced server-side. Pass idempotency_key only if the user gave you one — retrying with the same key never sends twice; do not invent one. Requires the Send Message module enabled on the account — on 403 "module not enabled", do NOT retry; tell the user to contact Sweeppea support. When a send is refused, call fetch_messaging_usage first: it is what distinguishes module access, plan channels, an exhausted allowance, a sending pause and a missing 10DLC number. Direct sending is a SEPARATE account switch from the module: fetch_messaging_usage can report ModuleEnabled true while DirectMessageEnabled is false, and this call then returns 403 "Direct messages through the API are not enabled for your account yet" (observed in production 2026-09-30). That is account configuration, not a bug — do NOT retry; tell the user to contact Sweeppea support.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYesemail, sms or both. both sends on each channel the participant has a usable address for
confirmYesMust be true. Set it ONLY after the user explicitly approved THIS action in this conversation, having been told what it does and that it cannot be taken back: a real email and/or SMS carrying this code goes out to the participant who holds it, and cannot be recalled. Never assume, never carry an approval over from a previous item, never set it to satisfy the schema.
coupon_tokenYesThe code token (UUID v4) of a code already assigned to a participant
idempotency_keyNoOptional, 8 to 64 characters [A-Za-z0-9_-]. Retrying with the same key never sends twice. Only pass one the user supplied

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: irreversible outbound delivery that cannot be recalled, server-side suppression and rate-limit enforcement, conditional idempotency via key, and the module-vs-DirectMessage account switch that produces a documented production 403. This is exactly the operational context annotations (readOnlyHint=false, openWorldHint=true) cannot convey.

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?

The irreversible-send warning and the confirm requirement are front-loaded, and every paragraph carries distinct operational payload. It is dense and the final 403 paragraph is long, but almost none of it is filler.

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?

For an irreversible, outbound, no-output-schema mutation, the definition covers prerequisites, approval gating, irreversibility, failure triage and the correct escalation path. Nothing an agent needs to call this safely 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%, so channel, confirm, coupon_token and idempotency_key are already documented, giving a baseline of 3. The description reinforces channel semantics and adds operational framing for idempotency_key ('do not invent one') and confirm (approval provenance), but no syntax or format detail beyond the schema.

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?

Opens with a specific verb+resource+scope: queue an assigned code to the participant who holds it, over email/SMS/both. The 'no address field: the recipient is whoever holds the code' clause implicitly separates it from the generic send_message/send_file siblings, so an agent can tell what this call is before opening the 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?

Explicit when-to-use and when-not-to-use: confirm=true only after per-participant approval, never carrying an approval over, and idempotency_key only when the user supplied one. It also routes the agent on failure paths ('when a send is refused, call fetch_messaging_usage first') and states do-NOT-retry conditions for two distinct 403s.

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

All Sweeppea MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources