Skip to main content
Glama

MeiSIM USA

Send a text

send_message

Send a text message from one of your MeiSIM numbers to a US number. Sending must be enabled on your account and each number has a monthly allowance; a refusal tells you which. The answer means accepted by the carrier: a mobile line has no delivery receipt. The same text to more than three numbers from one line inside an hour is refused (carriers drop that as a broadcast); write to each person in their own words. Not for emergency services. Needs your API key.

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": {
      "from": "<from>",
      "to": "<to>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe destination number, e.g. "+1 212 555 0100".
fromYesOne of your numbers.
messageYesThe text to send, up to 800 characters.

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
noteYes
sentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: it explains what a success response actually guarantees (carrier acceptance only, no delivery receipt on mobile lines), what causes a refusal and how to interpret it, the account-level enablement requirement, and the per-hour broadcast limit. These are non-obvious operational traits an agent cannot derive from readOnlyHint/openWorldHint alone.

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?

Front-loads the action and scope, then layers preconditions, semantics of the response, and rate-limit behavior, with no filler sentences. A few clauses are compressed to the point of being cryptic ("a refusal tells you which"), costing some readability without wasting space.

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

Completeness5/5

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

For a three-parameter send tool with annotations and an output schema, the description covers preconditions, refusal handling, delivery-receipt expectations, throttling, and exclusions. Nothing an agent needs in order to call it correctly or interpret the result is missing.

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 all three parameters are already documented. The description adds only marginal meaning – that `from` is the caller's own number and that `to` must be a US number – and implies one recipient per call via the three-numbers-per-hour rule, but gives no format or constraint detail beyond the schema.

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") and constrains scope to outbound messages from the user's own MeiSIM numbers to US numbers. It never names an alternative tool, so the separation from inbound siblings like wait_for_message or read_messages is left to inference rather than stated.

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 real preconditions (sending must be enabled, monthly allowance per number, API key), a hard usage boundary (no emergency services), and a throttling rule that changes behavior (same text to more than three numbers within an hour is refused). It stops short of naming any sibling tool as the alternative for a different need.

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.