Skip to main content
Glama

read_recent_messages

Retrieve recent iMessage conversations with a contact by phone number. Specify how many messages to fetch, up to 200.

Instructions

Read the recent X messages from the iMessage app between the user and the person with the phone number. X is defined based on the value of recent_message_count

Args: phone_number: The phone number of the person you want to retrieve the chat from recent_message_count: The recent messages to retrieve, can be a maximum of 200

Returns: A list of recent messages in the chat

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phone_numberYes
recent_message_countNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description only notes the maximum of 200 messages. It lacks disclosure of permissions, error handling, or side effects.

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?

The description is structured with Args and Returns sections, clear but slightly wordy. It efficiently conveys the tool's purpose without extraneous content.

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?

For a simple read tool, the description covers purpose, parameters, and return type adequately. The existence of an output schema (not shown) further supports completeness.

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?

Despite 0% schema coverage, the description explains both parameters with their roles and constraints, adding significant value beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool reads recent messages from iMessage using a phone number, distinguishing it from sibling tools like send_imessage or list_chats.

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?

The description implies usage for retrieving recent messages but does not explicitly guide when to use this versus alternatives like list_chats.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/altic-dev/altic-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server