TextForAgents

send_sms

Send an SMS text message from your TextForAgents number.

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

Input Schema

Name	Required	Description
`to`	Yes	Destination phone number in E.164 format, e.g. +18185550199.
`body`	Yes	The message text to send.
`from_number`	No	Your TextForAgents number to send from; defaults to your account's assigned number.
`idempotency_key`	No	Optional caller-chosen idempotency key: retrying the send with the same key returns the original message instead of sending (and charging) again. A fresh key is generated when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not disclose that sending is a billable action, whether delivery is synchronous, rate limits, or required permissions — notably, cost/charging is only hinted at inside the idempotency_key schema field, not the description.

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?

A single front-loaded sentence with no wasted words. It is efficient, though its brevity leaves the reader without the behavioral context a mutation tool warrants.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter outbound-messaging mutation with no annotations and no output schema, the description does not say what a successful call returns (message ID, status), whether it costs money, or how failures surface. The schema handles parameters, but the behavioral picture is incomplete.

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%, with each parameter self-documented including E.164 format, default from_number, and idempotency semantics. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Send') and resource ('an SMS text message') plus the scope ('from your TextForAgents number'). It is clearly distinguishable from read-only siblings get_balance and read_inbox, though it does not explicitly name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no reference to alternatives. The agent must infer that this is the outbound-messaging path versus read_inbox purely from the tool name.

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

All TextForAgents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?