Skip to main content
Glama
Sign In
agentring

agentring

by mutonby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

send_message

Sends a text message to the user's phone as a replyable notification, enabling an AI agent to deliver updates or ask questions and receive answers.

Instructions

Send a text message to the user's phone (it shows as a notification they can reply to).

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": {
      "text": "<text>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe message, max 4000 characters.
reply_toNoOptional msg_id or call_id this answers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses the delivery channel (phone notification the user can reply to), but says nothing about failure behavior, delivery guarantees, rate limits, or what the call returns.

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 tight sentence with the parenthetical earning its place by conveying delivery behavior. Front-loaded with the action, no filler.

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 simple two-parameter tool with no output schema and full schema coverage, the description covers the essentials but leaves gaps around result/confirmation and error handling that an agent might want before sending.

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 both 'text' (max 4000 chars) and 'reply_to' are already documented in the schema; the description adds only the reminder that the payload is a text message and omits any guidance on 'reply_to' threading semantics.

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 ('Send a text message to the user's phone') and adds the delivery mechanism, so the agent knows exactly what happens. It does not explicitly contrast with siblings like 'call', which would have pushed this to a 5.

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?

The parenthetical about the message arriving as a replyable notification implicitly signals asynchronous, non-interruptive use versus a live 'call', but there is no explicit when-to-use or when-not-to-use guidance and no mention of 'get_replies' or 'status'.

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

Deploy Server

Other Tools