Skip to main content
Glama

Send Text Message

send_message
Destructive

Send a message immediately via Mobile Text Alerts API. Use this tool for messages that need to be sent right away. For scheduling messages to be sent at a future time, use the schedule_message tool instead. The message goes out from the account's default number (the one it last sent from) unless from names another; the response's sentFrom says which was used, and notice carries anything to tell the user, such as a send from a limited trial number. PREREQUISITE: User must complete onboarding first (status must be 'ACTIVE'). If this tool returns 'Onboarding Required' error, immediately call get_onboarding_status to begin the onboarding flow.

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>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient phone number (can be formatted as +1234567890, 234-567-8900, (234) 567-8900, etc.)
fromNoSending phone number. Omit to use the account's default (the number it last sent from). Use list_sending_numbers to see options.
messageYesMessage content to send

Output Schema

NameRequiredDescriptionDefault
dataYesRaw Mobile Text Alerts API response envelope. The send payload is nested one level down, under `data.data` — e.g. `data.data.messageId`.
errorNo
noticeNoSomething the user should be told about this send, e.g. that it used a limited trial number
statusYes
contextNoAdditional context about why the call was blocked
successYes
sentFromNoThe number the message was sent from
errorCodeNoMachine-readable error code. 'ONBOARDING_REQUIRED' means the account has not finished brand registration. 'NO_SENDING_NUMBER' means no number on the account can send yet; 'SENDING_NUMBER_NOT_FOUND' / 'SENDING_NUMBER_UNAVAILABLE' mean the requested `from` number is not on the account or can't send. 'AUTH_FAILED', 'RATE_LIMITED', 'UPSTREAM_ERROR' and 'UPSTREAM_UNAVAILABLE' are Mobile Text Alerts API failures.
nextStepsNoExplicit recovery guidance for the calling agent
statusTextYes
formattedPhoneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses how the sender number is resolved (account default = last used number unless `from` overrides), points to the response fields `sentFrom` and `notice` that explain the outcome, and flags the trial-number notice case. The prerequisite and error-recovery behavior are also spelled out, which is unusually complete 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?

Front-loaded with purpose and the sibling alternative, then prerequisite and error handling; nearly every sentence carries actionable information. It is somewhat dense and the sender-resolution sentence overlaps with the schema's `from` documentation, but nothing is padded.

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?

Given an output schema exists, the description need not explain return values, yet it does highlight the one field that matters (`sentFrom`) and the `notice` field. Prerequisites, fallback tool routing, and sender defaults are all covered, leaving no gap that would cause a mis-call.

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 100%, so all three parameters are already documented in the schema, including the default-sender rule for `from`. The description restates rather than extends that semantics, adding only a pointer to the response's `sentFrom`, which is minimally 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?

States a specific verb and resource ('Send a message immediately via Mobile Text Alerts API') and immediately contrasts itself with the scheduling sibling, so an agent can tell which tool to pick without opening either 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 routing: use this for immediate sends, use schedule_message for future sends. It also states a hard prerequisite (account status must be 'ACTIVE') and prescribes a concrete recovery path ('immediately call get_onboarding_status') if the 'Onboarding Required' error is returned.

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