Skip to main content
Glama

List chats

list_chats
Read-onlyIdempotent

Lists recent iMessage and SMS conversations, newest first, and filters by name, phone number, or email to find the chat_id needed for other messaging actions.

Instructions

Lists recent iMessage/SMS conversations, newest activity first, optionally filtered by a name, phone number or email. Returns each chat's chat_id (used by the other tools), name, participants, service and last activity time. Group names are set by participants and are flagged as untrusted content.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum chats to return. Default 20, max 100.
queryNoFilter by chat name, contact name, phone number or email (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value: result ordering, the exact fields returned, and the security-relevant note that group names are participant-set and flagged as untrusted content.

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?

Three sentences, each earning its place: purpose and ordering first, then return shape, then the trust caveat. No filler and the most decision-relevant information is front-loaded.

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?

There is no output schema, so the description's enumeration of returned fields (chat_id, name, participants, service, last activity) is necessary and present. Gap is minor: it does not mention pagination behavior or how results behave when no filter matches, though the limit parameter is schema-documented.

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 both parameters are already documented, including the default 20 / max 100 limit and case-insensitive matching. The description restates the filter targets without adding syntax or behavioral nuance beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Lists recent iMessage/SMS conversations'), plus ordering ('newest activity first') and optional scoping. This is clearly distinguishable from siblings like get_messages and search_messages, which target message content rather than conversation enumeration.

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?

Implies usage through the note that chat_id is 'used by the other tools,' which hints this is the entry point for discovering conversations. However, it never states when to prefer this over search_messages or check_new_messages, nor any exclusions or prerequisites, leaving routing to inference.

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