Skip to main content
Glama
Hermoso

Hermoso

Official

Send an SMS or MMS

send_sms

Send SMS/MMS messages from brand Twilio or Telnyx numbers to one or up to 100 recipients; schedule sends and track delivery status.

Instructions

Send a text from one of the brand's own Twilio or Telnyx numbers: to (one number or a list of up to 100, E.164), text (up to 1,600 characters), media (up to 10 pictures for an MMS: a Library id, attachment://N or an https link), from (needed when the account has several numbers), sendAt (ISO time, to schedule it; on Twilio this needs a Messaging Service set with set_sms_settings). The answer has each message's id, segment count and status; delivery status follows (get_sms_status). Any optional sending settings the connection turned on (quiet hours, opt-out list) apply. No credits: the provider bills the account. Needs Twilio or Telnyx connected (Connectors, or connect_connector).

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

Input Schema

NameRequiredDescriptionDefault
toYes
fromNo
textNo
mediaNo
sendAtNo
providerNo
recipientTimezoneNoIANA zone, only used by quiet hours when the number does not tell it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.610

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, open-world write, and the description adds real context beyond that: provider billing with no credits consumed, the need for a connected Twilio/Telnyx account, and that connection-level settings (quiet hours, opt-out list) apply to sends. It doesn't spell out duplicate-send risk on retry, which the idempotentHint=false already flags but which is worth restating for a messaging 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 a single dense block rather than a list, but it is front-loaded with the core action and each parenthetical adds a real constraint (limits, formats, prerequisites) rather than filler. Slightly run-on, which costs it a point, but nothing is redundant.

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 7-parameter outbound-messaging tool with no output schema, the description covers what it does, what it costs, what prerequisites must exist, what response fields come back (id, segment count, status), and where delivery status lives. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at only 14%, the description carries the burden and does so thoroughly: recipient count cap and E.164 format for 'to', the 1,600-character limit for 'text', the 10-item MMS limit plus the three accepted media reference forms, and the ISO format and Twilio constraint for sendAt. Only 'provider' and 'recipientTimezone' (which has its own schema description) go unaddressed.

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 text from one of the brand's own Twilio or Telnyx numbers') and immediately scopes it to SMS/MMS via the media parameter. It also names the follow-up tool (get_sms_status) and the setup dependency (connect_connector), so the agent can place it without ambiguity.

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?

Gives conditional guidance for the optional fields: 'from' is needed when the account has several numbers, and sendAt on Twilio requires a Messaging Service configured via set_sms_settings. It also routes delivery tracking to get_sms_status. It does not state when not to use this tool (e.g. no SMS vs. other channel alternative), which keeps it below a 5.

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