Skip to main content
Glama

Send a text

send_text

Sends a text message to the phone number verified in your TextBot account. The recipient cannot be changed: it is always that verified number. Texts start with "TextBot: ". A normal text sent during your quiet hours is scheduled for when quiet hours end; an urgent text sends immediately. Counts toward your daily and monthly limits.

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

Input Schema

NameRequiredDescriptionDefault
messageYes
urgencyNonormal
allow_duplicateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the write, non-idempotent, open-world profile, and the description adds real context beyond them: the fixed recipient, the mandatory 'TextBot: ' prefix that alters the delivered content, quiet-hours deferral semantics, and consumption of daily/monthly quotas. It stops short of explaining what counts as a duplicate given allow_duplicate defaults to false, which matters for a non-idempotent send.

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?

Four short sentences, front-loaded with the resource and the fixed-recipient constraint, then behavior, then limits. Every sentence carries information an agent would otherwise have to guess at; nothing is redundant with the annotations.

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

Completeness3/5

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

For a mutation tool with no output schema, the description covers destination, content decoration, timing behavior, and quotas well. It omits duplicate-send semantics and the 480-character cap, both of which can cause incorrect calls, so it is adequate but not complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, yet it never names the parameters. Urgency is covered indirectly through the normal/urgent behavior, but message (1-480 chars) and especially allow_duplicate — whose default of false silently suppresses sends — are unexplained, leaving two of three parameters ambiguous.

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 ('Sends a text message') and immediately narrows scope: the recipient is always the verified number and cannot be changed. That scope statement alone separates it from schedule_text and cancel_scheduled_text without needing their schemas.

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 clear conditional guidance: a normal text during quiet hours is deferred to the end of quiet hours, while an urgent text sends immediately — so the agent knows how to choose between urgency values. It does not explicitly route to siblings (e.g. use schedule_text for future delivery, cancel_scheduled_text to undo), so it stops short of full when-to-use framing.

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