Skip to main content
Glama

list_chats

Read-onlyIdempotent

List recent chats—DMs, groups, project group chats—with unread counts and last-message times; filter by chat type or title substring.

Instructions

Chats (DMs, groups, project group chats), most recent first: id, title (DMs are titled with the other person's name), kind, unread count, last message time. Filter by kind "dm"|"group"|"project" or by a title substring. Chat arguments elsewhere accept ids or titles.

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
kindNo
limitNo
queryNo
only_unreadNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is fully covered. The description adds useful context beyond that: result ordering (most recent first) and the cross-tool convention that chat arguments accept ids or titles. It says nothing about pagination behavior for the default limit of 60, which is the main behavioral gap for a listing tool.

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?

A single dense sentence group with zero filler: the resource, ordering, and returned fields come first, then filtering, then the cross-reference note. Every clause carries information, including the DM-titling clarification that prevents a common misread.

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?

With an output schema present, listing return fields is optional, and rich annotations cover safety, so the description is close to sufficient for a four-parameter read tool. The missing pieces are meaningful for this tool type: no pagination semantics for limit, no clarification of whether only_unread composes with the other filters, and no explicit pointer to read_chat for fetching message bodies.

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 description coverage is 0%, so the description must carry parameter meaning. It does well for two of four: it supplies the kind enum values "dm"|"group"|"project" that the schema omits entirely, and explains query as a title substring. The limit and only_unread parameters get no mention at all, leaving half the parameters documented only by their names.

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 names a specific resource and scope: chats of three kinds (DMs, groups, project group chats), returned most recent first, with the exact fields exposed (id, title, kind, unread count, last message time). It even disambiguates DM titling. It stops short of naming the read-side sibling (read_chat) as the alternative for fetching a single conversation's content, so differentiation is implied rather than stated.

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?

It explains the two filtering modes (by kind or by title substring) and notes that chat arguments elsewhere accept ids or titles, which implies this is the discovery step before those calls. However, there is no explicit when-to-use or when-not-to-use guidance versus read_chat or get_project_chat, and no statement about when to use query versus kind.

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