Skip to main content
Glama

Send SMS — Premium (CIS / CN / MENA / Africa, Telnyx)

phone.telnyx.sms_premium

Send SMS to high-cost destinations (Russia, China, Turkey, MENA, Africa) at $0.25 per message. Verify pricing with Telnyx estimate_price before sending.

Instructions

⚡ ACTION: Send SMS to high-cost destinations: Russia +7, Belarus +375, Ukraine +380, China +86, Turkey +90, MENA (SA/AE/EG/JO/...), Africa (NG/KE/ZA/...), and any unknown prefix (default). $0.25/message. Highest tier — use telnyx.estimate_price to verify before sending (Telnyx)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient phone number in E.164 format (e.g. "+14155551234"). Trial accounts can only send to verified destination numbers added in the Telnyx portal.
fromYesSender phone number in E.164 format — must be a Telnyx number you own (e.g. "+15551234567"). Provision via Telnyx portal Numbers > Buy Numbers.
textYesSMS body text (max 1600 chars; >160 splits into multiple billing segments).
messaging_profile_idNoOptional Telnyx messaging profile UUID to route through a specific profile (10DLC campaign, sender pool).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior4/5

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

Annotations (readOnlyHint=false) confirm non-read behavior; description adds cost ($0.25/message) and destination scope. No contradictions, and the pricing detail provides useful behavioral context beyond annotations.

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?

Single sentence with emoji and key highlights is highly concise and front-loaded with essential information. 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?

Description covers purpose, usage guidance, and cost, and references an alternative tool for price estimation. With output schema present, return values are not needed. Slightly abstract on exact impact but sufficient for a sending action.

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?

Input schema has 100% coverage with detailed parameter descriptions. The description adds minimal extra semantic value (pricing context) but does not enhance understanding of parameters 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?

The description clearly states 'Send SMS to high-cost destinations' with specific country examples (Russia +7, China +86, etc.). Among siblings like phone.telnyx.sms_na and phone.telnyx.sms_world, this tool is uniquely identified as the premium tier for difficult regions.

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?

Explicitly notes 'Highest tier' and recommends using telnyx.estimate_price to verify cost before sending. This gives clear guidance on when to use and prerequisites, distinguishing from lower-cost alternatives.

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/whiteknightonhorse/APIbase'

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