Skip to main content
Glama

Hail Communication for AI

Send a text message

send_sms

Send an outbound text message.

    Without ``from_``, supported destinations use the workspace's alphanumeric sender ID.
    Other destinations use an eligible workspace SMS-capable number.
    A missing required number returns 422. SMS does not use the shared voice-call pool.
    US long-code texting to US recipients requires ready A2P 10DLC registration and an attached number.
    Trial texts (up to 25, only to the workspace's own verified phone, set up in the console): without from_, Hail uses one when the workspace's own number cannot text that US phone; set from_ to the trial number to use one directly. Each starts with "[Hail trial]".

    Hail does not verify consent.

    Returns the SMS ID, status, sender, destination, segment count and retry key, or an error.
    

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": {
      "to": "<to>",
      "body": "<body>",
      "recipient_consent": "<recipient_consent>"
    },
    "name": "send_sms"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient phone number in E.164 format, such as ``+14155551234``.
bodyYesMessage text. Long bodies are split into carrier segments.
from_NoSender: an active E.164 workspace number with SMS, from ``list_numbers``. Omitted: picked by destination (see the tool description).
metadataNoFree-form JSON object stored on the message record.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.
message_typeNo``informational`` for transactional or service messages, or ``marketing``.informational
consent_sourceNoWhere or how consent was obtained, such as ``signup form``. Required when ``message_type`` is ``marketing``.
idempotency_keyNoRetry key. The ``idempotency_key`` from an earlier response refers to that original request instead of starting a new one. Omitted: a new key is generated and returned.
recipient_consentYesAttestation that the recipient lawfully agreed to be contacted, as the user confirmed it. Hail does not check it; only ``true`` is accepted.
consent_obtained_atNoWhen consent was obtained, as an ISO 8601 timestamp, if known.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / recipient_consent / description
      Previous value: -"Attestation that the recipient lawfully consented to this contact. Only ``true`` is accepted."New value: +"Attestation that the recipient lawfully agreed to be contacted, as the user confirmed it. Hail does not check it; only ``true`` is accepted."
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations it discloses failure modes (422 for a missing required number), blast-radius facts (SMS does not draw on the shared voice-call pool), compliance requirements (A2P 10DLC for US long-code to US recipients), and the trial-message prefix '[Hail trial]'. It also states plainly that Hail does not verify consent, which is a meaningful behavioral admission for a mutation tool.

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?

It is front-loaded with the core action and then grouped into short, scannable clauses covering routing, errors, and returns. There is minor duplication: 'Hail does not verify consent' restates the recipient_consent schema text, and the return-value sentence is redundant given the output schema.

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 a 10-parameter mutation with an output schema, it covers routing logic, error conditions, compliance prerequisites, and trial behavior, which is everything an agent needs to call it correctly. The return summary is redundant but not harmful given a formal output schema exists.

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 baseline is 3, but the description earns a bump by explaining the destination-dependent sender resolution for from_ and the trial-number override that the schema only gestures at. The remaining parameters (metadata, llm_model, message_type, consent_source, idempotency_key) are left entirely to the schema text.

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 opening line states a specific verb and resource ('Send an outbound text message'), so there is no ambiguity about the operation. It does not explicitly name or differentiate itself from the sibling send_email, but the SMS-specific constraints (A2P 10DLC, segments, trial texts) make the domain unmistakable.

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?

It gives concrete routing conditions: without from_ the workspace alphanumeric sender ID or an eligible SMS-capable number is used, and trial texts apply only to the workspace's own verified phone (25 max). It stops short of explicit when-not-to-use or naming an alternative tool, but the prerequisites (A2P registration, attached number) tell an agent when this call will fail.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources