Skip to main content
Glama

Recent texts and replies

list_recent_texts
Read-onlyIdempotent

Lists recent texts TextBot sent to your phone and the replies you texted back, newest first. Reply text is written by the phone's owner. Scheduled texts that have not gone out appear with status "scheduled".

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": "list_recent_texts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
directionNoall
since_hoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is largely covered. The description adds real context beyond them: ordering is newest-first, reply text is authored by the phone's owner rather than the bot, and pending scheduled texts are included with status "scheduled" — an important disclosure that the result set mixes sent and unsent messages.

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?

Three tight sentences with no filler; the core scope and ordering arrive first and the scheduled-status caveat follows. Slight redundancy between 'recent texts TextBot sent' and 'replies you texted back', but it earns its place by clarifying both halves of the dataset.

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 read-only list tool with no output schema, the description should sketch the returned record shape or pagination behavior; it only implies a status field via the "scheduled" note. Combined with the undocumented limit and since_hours parameters, an agent can call it correctly but cannot predict the result volume or structure.

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% across three parameters, so the description must carry the load and largely does not. The mention of both sent texts and replies loosely maps to the direction enum and the status mention hints at the return field, but limit (default 20, max 50) and since_hours (max 720) are never explained, including what happens when they are omitted.

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 with scope: recent texts TextBot sent plus the owner's replies, returned newest first. The addition that unsent scheduled texts appear with status "scheduled" sharpens what counts as a 'recent text'. It never names a sibling (e.g. get_text_status, send_text), so differentiation is left implicit.

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?

Usage is only implied — an agent can infer this is the tool for reviewing recent conversation history or checking whether a scheduled text went out. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as get_text_status for a single message or cancel_scheduled_text for removing a pending one.

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