list_message_chats

Retrieve recent iMessage conversations from macOS Messages. Enables AI agents to view chat history and access message threads for workflow automation and reference.

Instructions

List recent iMessage conversations

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.js:82-86 (registration)

Tool registration loop where list_message_chats is registered as a stub. All tools are registered with empty schemas and a placeholder response indicating this is just an inspection stub.

for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
  }));
}

server.js:36-36 (schema)
Tool definition entry for list_message_chats in the TOOLS array - this is where the tool name and description are defined.
```
["list_message_chats", "List recent iMessage conversations"],
```

Tool Definition Quality

B3.2/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 full disclosure burden. While it notes 'recent' (implying a time/filter constraint), it fails to specify what 'recent' means (e.g., last 30 days, last 100 conversations), doesn't indicate this is a read-only/safe operation, and doesn't describe the return format or pagination behavior.

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?

The description is a single, efficient sentence with no waste. It front-loads the action and scope, which is appropriate for a zero-parameter tool where complexity is minimal.

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?

Given the tool's simplicity (no params, straightforward list operation), the description is minimally adequate. However, without an output schema, it should ideally describe what constitutes a 'conversation' object (e.g., participant names, last message date) and define the 'recent' scope to be complete.

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?

The input schema has zero parameters, which per guidelines establishes a baseline score of 4. The description appropriately requires no additional parameter explanation given the simple list-all behavior.

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?

The description provides a clear verb ('List') and resource ('iMessage conversations'), and specifies the domain ('iMessage') which distinguishes it from sibling tool 'teams_list_chats'. However, it doesn't clarify the distinction between 'conversations' (threads) and individual 'messages', which would help differentiate from 'read_messages' and 'search_messages'.

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?

No guidance provided on when to use this versus 'read_messages', 'search_messages', or 'teams_list_chats'. No mention of prerequisites (e.g., requiring macOS with Messages access) or typical workflow (e.g., use this first to get chat IDs, then read_messages to get content).

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

Install Server

Pilot MCP