RepoChatMCP

by gzmagyari

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

chat.read_session

Read messages from a specific session by its ID. Filter by message type, limit, or index range for targeted retrieval.

Instructions

Read messages from a specific session.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "chat.read_session"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max messages (default 100)
`types`	No	Filter by message types
`endIndex`	No	End message index
`provider`	No	Provider hint: claude or codex
`sessionId`	Yes	Session ID to read
`startIndex`	No	Start message index

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.11Aug 2, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Read messages' but does not explain message ordering, pagination behavior, default limits, error handling, or implications of the 'limit' and 'startIndex' parameters. It's a minimal read operation but lacks depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no fluff, but it is under-specified. It states the core purpose but does not earn its place by adding value beyond the tool name; however, since the title is null, it serves as the only textual anchor. It is concise but could be more informative without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 6 parameters, no output schema, and no annotations, the description is incomplete. It fails to explain the meaning of message types, index ranges, or provider hints, and does not describe the return format. The user would need to rely heavily on parameter names and examples.

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 the baseline is 3. The description does not add any extra semantics beyond what the schema already provides, which is acceptable given the high coverage.

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 clearly states the action (read) and the resource (messages from a specific session). It is specific enough to distinguish from generic tools, though it doesn't explicitly differentiate it from similar sibling tools like chat.read_lines or chat.search.

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?

The description provides no guidance on when to use this tool vs alternatives such as chat.list_sessions, chat.search, or chat.read_lines. There is no mention of context, prerequisites, or exclusions.

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

Deploy Server