Skip to main content
Glama
Sign In
express-reader-mcp

express-reader-mcp

by Eflarus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

express_list_chats

Lists eXpress chats with name, type, unread count, and last-activity metadata; filter by name or transliteration, or show only unread chats.

Instructions

List chats with metadata (name, type, unread count, last-activity time). Side-effect-free. Use query to filter by name/transliteration, unreadOnly to show only unread.

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": "express_list_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax chats (default 40)
queryNoFilter by name or transliteration (e.g. 'иванов' or 'ivanov')
unreadOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full load, and "Side-effect-free" usefully declares the read-only nature. However, it says nothing about ordering of results, pagination beyond `limit`, or whether chats are scoped to a workspace/account, which are the traits an agent would want before calling.

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?

Three compact sentences with the resource and returned fields front-loaded and the filter hints last. Nothing is redundant, though the parenthetical metadata list could be trimmed if brevity were prioritized over precision.

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?

For a simple three-parameter read tool with no output schema and no annotations, the description covers purpose and filter semantics adequately. It is still missing result ordering and scope information, which an agent needs to interpret a truncated list correctly.

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?

Schema coverage is 67%: `query` and `limit` are documented in the schema, while `unreadOnly` has none. The description compensates by explaining `query` matches name or transliteration and that `unreadOnly` restricts to unread chats, adding real meaning beyond the schema. Only `limit` behavior is left entirely to the schema.

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 opens with a specific verb and resource ("List chats") and even enumerates the metadata returned (name, type, unread count, last-activity time), which cleanly separates it from express_list_threads and express_read_chat. It stops short of naming those siblings explicitly, so differentiation is implicit 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?

Usage is only implied: the description explains what `query` and `unreadOnly` do, which hints at when to reach for them, but it never states when to use this tool versus express_list_threads or express_search_messages. There are no exclusions or preconditions given.

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

Deploy Server

Other Tools