Skip to main content
Glama
WebisityStudio

claude-codex-mcp-bridge

by WebisityStudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read a thread

bridge_thread

Read one page of a conversation thread: omit a cursor to get the latest messages, use beforeId to page older or afterId to page newer.

Instructions

Read one page of a conversation thread. Without a cursor it returns the most recent messages; pass beforeId (olderBeforeId) to page back or afterId (newerAfterId) to page forward.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum messages to return. Defaults to 25 (30 for threads).
afterIdNoReturn messages newer than this id.
beforeIdNoReturn messages older than this id.
maxCharsNoCharacter budget for the whole result. Defaults to 48000 so MCP hosts never truncate it.
threadIdYesThread identifier to fetch.
maxBodyCharsNoPreview mode: shorten every body to this many characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.0
    • addedInput schema / properties / afterId
      Added value: +{
+  "description": "Return messages newer than this id.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / beforeId
      Added value: +{
+  "description": "Return messages older than this id.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum messages to return. Defaults to 25 (30 for threads).",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / maxBodyChars
      Added value: +{
+  "description": "Preview mode: shorten every body to this many characters.",
+  "maximum": 400000,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / maxChars
      Added value: +{
+  "description": "Character budget for the whole result. Defaults to 48000 so MCP hosts never truncate it.",
+  "maximum": 400000,
+  "minimum": 1000,
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A3.7/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 discloses the default behavior (most recent messages) and the paging model, which goes beyond the schema, but says nothing about read-only nature, auth/permission requirements, ordering guarantees, or return shape.

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 filler. The core behavior (returns most recent by default) is front-loaded ahead of the paging instructions.

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 six-parameter read tool with no annotations and no output schema, the description covers pagination but omits return structure, ordering, and the truncation/budget behavior implied by maxChars and maxBodyChars. Adequate but with clear gaps.

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 coverage is 100%, so all six parameters are already documented. The description reinforces the cursor semantics (olderBeforeId/newerAfterId) but adds little beyond what the schema states per parameter, matching the baseline for full 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?

States a specific verb and resource ('Read one page of a conversation thread'), and the 'one page' qualifier immediately scopes it. It does not explicitly distinguish itself from siblings like bridge_inbox or bridge_outbox, so it falls short of a 5.

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?

Gives clear operational context for the cursor parameters: no cursor returns the most recent messages, beforeId pages back, afterId pages forward. It does not state when to choose this tool over sibling read tools such as bridge_inbox, so it stops short of naming alternatives/exclusions.

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