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

express-reader-mcp

by Eflarus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

express_list_threads

Lists threads for a given chat with thread IDs and reply counts, enabling you to choose a thread ID to read its messages.

Instructions

List the threads belonging to a chat (threadId + reply count). Side-effect-free. Use the returned threadId with express_read_thread.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chatId": "<chatId>"
    },
    "name": "express_list_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully declares "Side-effect-free" and describes the returned fields, but omits ordering, pagination, and error 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?

Two tight sentences with zero waste. The core purpose is front-loaded, followed by safety and next-step guidance.

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 one-parameter read tool with no output schema, the description covers purpose, safety, returned fields, and the follow-up tool. Pagination and ordering are the main omissions.

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?

The only parameter is chatId, and the phrase "belonging to a chat" maps it to the chat identifier. However, with 0% schema description coverage, the description does not explain the chatId format or constraints.

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 states a specific verb and resource: "List the threads belonging to a chat." It also names the returned fields and explicitly points to express_read_thread for follow-up, making it distinguishable from that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly implies the tool is for enumerating threads within a chat and gives a follow-up path via express_read_thread. It does not state when not to use it or compare it with other listing/search tools.

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