Skip to main content
Glama

Read received texts

read_messages
Read-only

Retrieve text messages received on your MeiSIM numbers, newest first, and filter by number or timestamp to follow conversations. Use the last seen received_at as since to fetch only newer messages.

Instructions

Read the text messages received on your MeiSIM numbers, newest first. Filter to one number and/or to messages after a timestamp. To follow a conversation, pass the received_at of the last message you saw as since. 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": "read_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50.
sinceNoISO 8601 timestamp; only messages received after it.
numberNoOne of your numbers, e.g. "4234322309" or "+1 423 432 2309". Omit for all numbers.

Output Schema

NameRequiredDescriptionDefault
noteNo
countYes
messagesYes
newest_received_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.5

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and open-world, so the description is free to add the traits that matter: result ordering (newest first), combinable filters, and the API-key requirement. It does not discuss rate limits or result-size behavior, which keeps it below a 5.

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 core action and ordering, then filters, then the conversation-following tip, then the auth note. No redundancy with the title or schema.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and the description covers ordering, filtering and auth adequately for a zero-required-parameter read tool. Minor gap: it doesn't say how to page past the limit cap or what the default ordering means for offsets.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema for `since` by tying it to the received_at of the last message seen for conversation continuity. It also clarifies that the number filter is optional and combinable. `limit` is left entirely to 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 ("Read the text messages received on your MeiSIM numbers") plus the scope and ordering ("newest first"), which is clearer than the title alone. It does not explicitly name a contrasting sibling such as send_message or wait_for_message, so sibling differentiation is left to inference.

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 usage context: filter to one number and/or a timestamp, and a concrete recipe for following a conversation ("pass the received_at of the last message you saw as since"). It stops short of stating when-not to use it or naming an alternative tool.

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