Skip to main content
Glama

Schedule a text

schedule_text

Schedules a text message to your verified phone for a time 16 minutes to 35 days from now. Counts toward your limits when scheduled.

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

Input Schema

NameRequiredDescriptionDefault
messageYes
send_atYes
allow_duplicateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the operation as non-readOnly, openWorld, non-idempotent, and non-destructive. The description adds meaningful context about delivery to a verified phone and quota consumption, but it does not discuss duplicate handling, cancellation implications, or what happens at send time.

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?

Two concise sentences, front-loaded with the core purpose and key scheduling bounds. There is no filler or unnecessary wording.

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?

The core scheduling constraints are covered, but with no output schema and zero schema description coverage, the definition omits what the call returns and how allow_duplicate affects behavior. Adequate for basic invocation, but not fully 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%, and the description only clarifies the schedule window and verified-phone target. It leaves the message constraints and the allow_duplicate parameter undocumented, which is a notable gap for a three-parameter tool.

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 and resource: schedules a text message to the user's verified phone. The scheduling window adds useful specificity, though no sibling tool is named to sharpen differentiation from send_text.

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

Usage Guidelines3/5

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

Gives a practical scheduling constraint (16 minutes to 35 days) and notes quota impact, but does not explicitly say when to use this instead of send_text, list_recent_texts, or cancel_scheduled_text.

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