Skip to main content
Glama

Dial by Aloha Labs

read_text_messages

Read recent text messages received on one of your numbers.

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": {
      "api_key": "<api_key>",
      "number_id": "<number_id>"
    },
    "name": "read_text_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
api_keyYesYour Dial API key (from sign_up)
number_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully says 'received' (inbound only, not sent messages), but omits ordering (newest-first?), default limit, pagination behavior, and whether api_key scoping restricts results to the account.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of the missing detail flagged elsewhere rather than through deliberate compression.

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

Completeness2/5

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

With three parameters, 33% schema coverage, no annotations, and no output schema, the description should clarify return shape, ordering, and pagination. Instead it gives one sentence, leaving the agent under-informed about what comes back and how many messages.

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 coverage is only 33% — api_key is documented, but number_id and limit have no schema descriptions. The description gestures at 'one of your numbers' (number_id) and 'recent' (limit), but gives no format, default, or range semantics, so the gap is not compensated.

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?

Specific verb ('Read') plus a specific resource ('text messages') with a scope qualifier ('recent', 'received on one of your numbers'). No sibling tool covers inbound SMS, so the agent can identify the right tool, though the description does not explicitly name what it is not (e.g., get_call_result).

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?

States nothing about when to call this versus alternatives, or what prerequisites exist (a valid number_id from list_phone_numbers). The only implicit signal is 'received on one of your numbers', leaving the agent to infer setup steps.

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.