Skip to main content
Glama
Ringer

warp-mcp

by Ringer

Send an SMS message

msg_send

Send a real SMS text message to any phone number. The message is delivered immediately to the recipient's device.

Instructions

SENDS A REAL SMS TEXT MESSAGE to a real phone number — the recipient's device will receive it immediately; there is no test/sandbox mode, so confirm the destination and body before calling. The from number must be assigned to your account AND enrolled in an approved 10DLC campaign (register via msg_create_brand → msg_create_campaign → msg_assign_numbers), otherwise the request is rejected. Errors: INVALID_PAYLOAD/MISSING_PARAM/INVALID_TO (400), NO_ACTIVE_CUSTOMER/UNAUTHORIZED (401), FROM_* rejections for unenrolled numbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesDestination telephone number in E.164 / NANP format, e.g. "13125551212". A real device receives the message.
bodyYesMessage text, e.g. "Your verification code is 123456". Encoding (GSM-7 vs UCS-2) and segment count are computed automatically.
fromYesSending telephone number in NANP format, e.g. "13039813633". Must be assigned to your account and enrolled in an approved 10DLC campaign (see msg_list_numbers).
idempotency_keyNoClient-supplied Idempotency-Key: retrying with the same key returns the original message instead of sending a duplicate. Strongly recommended.
status_callbackNoOptional webhook URL that receives message-status callbacks (queued → sent → delivered/failed), e.g. "https://example.com/webhooks/sms"
Behavior4/5

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

The description discloses key behaviors beyond annotations: immediate real message delivery, no sandbox mode, enrollment requirement for 'from' number, idempotency behavior, and status callback capability. Annotations are all false, so the description carries the full burden, which it meets well.

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?

The description is concise at three sentences, each earning its place: first sentence states purpose and warning, second sentence covers prerequisites, third sentence lists error codes. The most critical information is front-loaded.

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 the lack of output schema and presence of 5 parameters (3 required), the description covers the real-world impact, prerequisites, error handling, idempotency, and optional callback. No significant gaps remain for safe and correct tool usage.

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 baseline is 3. The description adds marginal value by repeating some schema details (e.g., from number enrollment) but does not add new meaning or examples beyond what is already in the input schema properties.

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?

The description starts with a clear verb 'SENDS' and identifies the resource as 'a real SMS text message', immediately distinguishing this tool from sibling tools that manage brands, campaigns, or numbers. The specificity about immediate delivery and lack of test mode reinforces its unique purpose.

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?

The description provides strong usage context: it warns about the real-world impact, lists prerequisites (from number enrolled in 10DLC campaign), and cites error codes. Although it does not explicitly name alternatives or state when not to use, the guidance is sufficient for safe invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Ringer/warp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server