Skip to main content
Glama

Hail Communication for AI

List text messages

list_sms
Read-onlyIdempotent

List recent workspace text messages.

    Returns ``items`` and ``next_cursor``.

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_sms"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly items sent to this E.164 phone number.
limitNoHow many items one page holds. ``next_cursor`` in the response points to the next page.
cursorNoPagination cursor: the ``next_cursor`` from the previous page. Omitted: the first page.
statusNoOnly messages currently in this status; ``received`` means inbound. Omitted: every status.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of items per page."New value: +"How many items one page holds. ``next_cursor`` in the response points to the next page."
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. Changed5 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Page size, 1 to 200."New value: +"Number of items per page."
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / status / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "queued",
      +      "sent",
      +      "delivered",
      +      "failed",
      +      "undelivered",
      +      "received"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / status / description
      Previous value: -"Only messages in this status: queued, sent, delivered, failed, undelivered or received."New value: +"Only messages currently in this status; ``received`` means inbound. Omitted: every status."
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered without help from the description. The description adds only modest extra context: results are scoped to 'recent' messages and to the workspace. It says nothing about default ordering, retention window, or pagination limits beyond the response keys.

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?

Two short sentences with the operation front-loaded and no filler. The second sentence describing return keys is largely redundant because an output schema exists, which is the only minor waste.

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 simple read-only paginated list tool with full schema coverage, an output schema, and clear annotations, the description covers what an agent needs to select and call it correctly. Missing filter details live in the schema, and return values are covered structurally.

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 every parameter (to, limit, cursor, status, llm_model) is already fully documented in the schema, including the enum meaning of 'received' and pagination behavior. The description adds no filter or formatting detail beyond the schema, so the baseline of 3 applies.

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 ('List recent workspace text messages'), so the agent knows this is a read/list operation over SMS messages. It does not distinguish itself from siblings such as get_sms (single-message fetch) or send_sms, but the list-vs-single distinction is reasonably implied by the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no mention of when not to use it, and no pointer to alternatives like get_sms for a single message. The agent must infer that this is the paginated browsing tool purely from the word 'List' and the presence of a cursor parameter.

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