Skip to main content
Glama

MeiSIM USA

Wait for the next text

wait_for_message
Read-only

Wait for the next text message on one of your MeiSIM numbers and return it. Blocks up to timeout_seconds (default 30, max 50). Pass since as the time you started waiting (default: now) so an older message is not mistaken for the new one. If nothing arrives, received is false; call again to keep waiting. Needs your API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wait_for_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO 8601; only a message received after this counts. Default: now.
numberNoOne of your numbers. Omit to watch every number on the account.
timeout_secondsNoHow long to wait, default 30.

Output Schema

NameRequiredDescriptionDefault
noteNo
sinceYes
messagesYes
receivedYes
waited_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the annotations: blocking semantics, timeout bounds (default 30, max 50), the no-message outcome ('received is false'), the retry loop, and the API key requirement. The only gap is that other failure modes (bad number, auth failure, rate limiting) are not described.

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 blocking wait and its duration, then the since-window rationale, then the empty-result and retry contract, then auth. No filler and nothing redundant.

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 blocking-poll tool with an output schema and full annotation coverage, the description supplies everything an agent needs: duration bounds, staleness avoidance, empty-result handling, retry behavior, and the auth prerequisite.

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%, so all three parameters are already documented in the input schema. The description adds genuine meaning only for 'since' — pass the time you started waiting so an older message is not mistaken for a new one — while number and timeout_seconds are simply restated. Baseline 3 fits.

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: 'Wait for the next text message on one of your MeiSIM numbers and return it.' The emphasis on 'next' implicitly separates it from the read_messages sibling, but no sibling is named explicitly, so differentiation is inferred rather than spelled out.

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 operational guidance: it is a blocking wait bounded by timeout_seconds, and 'call again to keep waiting' tells the agent how to continue polling. It also warns against reusing a stale window via 'since'. Missing an explicit statement of when to prefer read_messages over waiting.

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.