Agent Broker

send_message

Destructive

Send a message on behalf of an agent's user or an SMB via WhatsApp or email — both live. SMS and voice are advertised but NOT wired on this deployment: they always fail honestly (channel_not_configured), uncharged. Sent immediately, no scheduling. Every send passes a non-bypassable gate (TCPA, GDPR, CASL, PDPL, 26 jurisdictions): marketing without recorded consent gets a structured compliance_violation receipt. [from $0.02/call, variable] [async→get_outcome]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`content`	Yes
`recipient`	Yes
`business_id`	No	Stable id for the recipient business; used for global demand shaping.
`message_type`	Yes	Intent tag for the message. Five permitted types. 'marketing' is allowed only…
`on_behalf_of`	No	Who this message is FOR (your end-user's name/label). On WhatsApp this opens a…
`idempotency_key`	No	Retry key: a 24h replay returns the original receipt, not re-run or charged.
`preferred_channel`	No		auto

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 22, 2026

changedInput schema / properties / business_id / description

Previous value: -"Optional stable id for the recipient business. Enables global demand shaping…"New value: +"Stable id for the recipient business; used for global demand shaping."

changedInput schema / properties / idempotency_key / description

Previous value: -"Optional client-supplied key for safe retries. Replaying the same key within 24h returns the original receipt - the operation is NOT re-executed and NOT re-charged."New value: +"Retry key: a 24h replay returns the original receipt, not re-run or charged."

removedInput schema / properties / send_at_iso

Removed value: -{
-  "description": "NOT SUPPORTED YET. We do not schedule messages. Supplying a time more than 2…",
-  "format": "date-time",
-  "type": "string"
-}

Changed4 schema fields changedSep 10, 2026

changedInput schema / properties / business_id / description

Previous value: -"Optional stable id for the recipient business. Enables global demand shaping (we rate-limit total inbound across ALL agents so businesses stay responsive instead of blocking us)."New value: +"Optional stable id for the recipient business. Enables global demand shaping…"

changedInput schema / properties / message_type / description

Previous value: -"Intent tag for the message. Five permitted types. 'marketing' is allowed only when paired with a valid consent_record_id; the compliance gate verifies the consent at send time and rejects (compliance_violation receipt) if it's missing, expired, or revoked."New value: +"Intent tag for the message. Five permitted types. 'marketing' is allowed only…"

changedInput schema / properties / on_behalf_of / description

Previous value: -"Who this message is FOR (your end-user's name/label). On WhatsApp this opens a tracked conversation and travels in-message as '#4821 for Sara (via HatchLoop)', so the business knows who it is talking to and their reply is matched back to this exact request instead of guessed. Strongly recommended for two-way channels."New value: +"Who this message is FOR (your end-user's name/label). On WhatsApp this opens a…"

changedInput schema / properties / send_at_iso / description

Previous value: -"NOT SUPPORTED YET. We do not schedule messages. Supplying a time more than 2 minutes in the future is REFUSED (reason_code scheduling_not_supported) rather than sent immediately, which is what used to happen. Call send_message at the moment you want delivery, or omit this field."New value: +"NOT SUPPORTED YET. We do not schedule messages. Supplying a time more than 2…"

Changed1 schema field changedAug 30, 2026

changedInput schema / properties / send_at_iso / description

Previous value: -"Schedule for future delivery; omit for immediate"New value: +"NOT SUPPORTED YET. We do not schedule messages. Supplying a time more than 2 minutes in the future is REFUSED (reason_code scheduling_not_supported) rather than sent immediately, which is what used to happen. Call send_message at the moment you want delivery, or omit this field."

Changed2 schema fields changedAug 26, 2026

addedInput schema / properties / business_id

Added value: +{
+  "description": "Optional stable id for the recipient business. Enables global demand shaping (we rate-limit total inbound across ALL agents so businesses stay responsive instead of blocking us).",
+  "type": "string"
+}

addedInput schema / properties / on_behalf_of

Added value: +{
+  "description": "Who this message is FOR (your end-user's name/label). On WhatsApp this opens a tracked conversation and travels in-message as '#4821 for Sara (via HatchLoop)', so the business knows who it is talking to and their reply is matched back to this exact request instead of guessed. Strongly recommended for two-way channels.",
+  "type": "string"
+}

Changed1 schema field changedAug 25, 2026

changedInput schema / properties / preferred_channel / enum

Previous value: -[
-  "sms",
-  "email",
-  "voice",
-  "auto"
-]New value: +[
+  "whatsapp",
+  "sms",
+  "email",
+  "voice",
+  "auto"
+]

Changed1 schema field changedAug 25, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Optional client-supplied key for safe retries. Replaying the same key within 24h returns the original receipt - the operation is NOT re-executed and NOT re-charged.",
+  "maxLength": 128,
+  "type": "string"
+}

Changed2 schema fields changedMay 24, 2026

changedInput schema / properties / message_type / description

Previous value: -"Intent tag — must match the consumer-initiated transactional flow being completed. 'marketing' is not a permitted value; messages tagged as marketing are rejected by the compliance gate."New value: +"Intent tag for the message. Five permitted types. 'marketing' is allowed only when paired with a valid consent_record_id; the compliance gate verifies the consent at send time and rejects (compliance_violation receipt) if it's missing, expired, or revoked."

changedInput schema / properties / message_type / enum

Previous value: -[
-  "transactional",
-  "reminder",
-  "follow_up",
-  "notification"
-]New value: +[
+  "transactional",
+  "marketing",
+  "reminder",
+  "follow_up",
+  "notification"
+]

Changed2 schema fields changedMay 19, 2026

addedInput schema / properties / message_type / description

Added value: +"Intent tag — must match the consumer-initiated transactional flow being completed. 'marketing' is not a permitted value; messages tagged as marketing are rejected by the compliance gate."

changedInput schema / properties / message_type / enum

Previous value: -[
-  "transactional",
-  "marketing",
-  "reminder",
-  "follow_up",
-  "notification"
-]New value: +[
+  "transactional",
+  "reminder",
+  "follow_up",
+  "notification"
+]

First observedMay 5, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare readOnly=false, destructive=true, and idempotent=false, and the description adds substantial value beyond them: channel failure modes (unconfigured SMS/voice), immediate send with no scheduling, a non-bypassable multi-jurisdiction compliance gate, pricing, and an async→get_outcome handoff. The idempotency_key schema detail complements, not contradicts, the idempotentHint=false annotation.

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?

Every sentence carries distinct information: scope, live channels, non-wired channels, immediacy, compliance gate, pricing, and async routing. The purpose is front-loaded and the bracketed tags ([from $0.02/call] [async→get_outcome]) at the end are highly skimmable. No wasted words.

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

Completeness4/5

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

For a complex 7-parameter, no-output-schema tool, the description covers channels, failure behavior, compliance constraints, cost, and the async outcome path — quite complete. It does not describe the success receipt/return shape (which matters since there is no output schema), nor does it route to send_transactional_confirmation, so it is not a 5.

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 coverage is 57%, so the description must partially compensate. It does add meaning for the channel enum (sms/voice will fail; whatsapp/email are live) and for message_type ('marketing' requires recorded consent). But it does not clarify recipient construction (id_type/id_value semantics), content.template_vars usage, or the truncated 'marketing is allowed only…' schema note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('Send a message on behalf of an agent's user or an SMB') and names the live channels (WhatsApp/email). It is clear but does not differentiate from the close sibling send_transactional_confirmation, which likely overlaps in scope, so it falls short of a 5.

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?

Provides clear context and explicit when-not guidance: SMS/voice are 'NOT wired' and fail with channel_not_configured, and marketing without recorded consent produces a compliance_violation receipt. However, it never mentions the alternative tool send_transactional_confirmation or says when to prefer it, so it lacks the explicit alternative routing needed for a 5.

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

All Agent Broker tools Inspect

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.

send_message

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources