Skip to main content
Glama
Sign In
codex-mcp-bridge

codex-mcp-bridge

by buidangminh23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Read a Codex thread

read_codex_thread
Read-only

Read a Codex thread without sending anything. Pass the exact turnId to get authoritative assistant items, text, and reply hash; without it, recent history may omit items.

Instructions

Read a Codex thread without sending anything. In Desktop mode, pass the exact turnId returned by send_to_codex_thread for authoritative assistant item IDs, text, and reply hash; without turnId the native recent-history view may omit items.

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": {
      "threadId": "<threadId>"
    },
    "name": "read_codex_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent messages to show (default 10)
turnIdNoExact turn id to inspect authoritatively in Codex Desktop mode
threadIdYesCodex thread id
responsePreferencesNoOpt in to versioned filtered responses and cursor delivery; omitted preserves existing behavior. Inspect the returned envelope and follow nextCursor with the same tool and selector.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.23.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv1.22.2
    • addedInput schema / properties / responsePreferences
      Added value: +{
+  "additionalProperties": false,
+  "description": "Opt in to versioned filtered responses and cursor delivery; omitted preserves existing behavior. Inspect the returned envelope and follow nextCursor with the same tool and selector.",
+  "properties": {
+    "delivery": {
+      "additionalProperties": false,
+      "properties": {
+        "options": {
+          "additionalProperties": false,
+          "properties": {
+            "cursor": {
+              "maxLength": 512,
+              "minLength": 1,
+              "type": "string"
+            },
+            "maxBytes": {
+              "maximum": 98304,
+              "minimum": 8192,
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "type": {
+          "const": "cursorPagination",
+          "type": "string"
+        }
+      },
+      "required": [
+        "type"
+      ],
+      "type": "object"
+    },
+    "filter": {
+      "additionalProperties": false,
+      "properties": {
+        "includeReasoning": {
+          "type": "boolean"
+        },
+        "includeToolPayloads": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  3. Changed1 schema field changedv1.16.1
    • addedInput schema / properties / turnId
      Added value: +{
+  "description": "Exact turn id to inspect authoritatively in Codex Desktop mode",
+  "type": "string"
+}
  4. First observedv1.11.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds meaningful behavioral context beyond that: passing turnId yields authoritative assistant item IDs, text, and a reply hash, while omitting it may cause the native recent-history view to omit items. It stops short of covering error cases or pagination behavior, keeping it at a 4.

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 sentences, front-loaded with the core action and a mode-specific caveat. Every clause carries actionable information, with no repetition or filler.

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?

There is no output schema, but the input schema's responsePreferences description covers the response envelope and cursor pagination. The description focuses on the key behavioral caveat around turnId; it could say more about response filtering or default return shape, but it is sufficient for correct invocation.

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 100%, so the baseline is 3. The description still adds real value for turnId by naming its source (send_to_codex_thread) and explaining its effect (authoritative items vs. possible omissions), which goes beyond the schema's one-line parameter description.

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 uses a specific verb and resource ('Read a Codex thread') and immediately scopes it with 'without sending anything,' distinguishing it from send_to_codex_thread. It does not explicitly differentiate from open_codex_thread or list_codex_threads, so sibling separation is only partially addressed.

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 gives a conditional usage rule for turnId in Desktop mode and warns that omitting turnId can produce incomplete history. However, it does not state when to use this tool versus open_codex_thread, wait_codex_reply, or list_codex_threads, so guidance is implied rather than explicit.

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