Skip to main content
Glama
buidangminh23

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. 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.

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.

Input Schema

TableJSON 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.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"
+}
  2. 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"
+}
  3. 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 and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond them: mode-dependent behavior in Desktop mode and the caveat that omitting turnId 'may omit items' in the native recent-history view. It also hints at returned content (assistant item IDs, text, reply hash) despite no output schema, though return format is not fully described.

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 dense sentences with zero filler: the first states the action and its non-mutating nature, the second front-loads the critical mode-specific parameter caveat. Nothing is redundant with the schema or annotations.

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 read-only tool with annotations covering the safety profile and 100% schema coverage, the description supplies the mode-specific nuance an agent needs to call it correctly. The responsePreferences/cursor pagination parameter is left entirely to the schema, which is acceptable but leaves the pagination workflow only lightly signposted.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining the provenance and purpose of turnId ('the exact turnId returned by send_to_codex_thread for authoritative assistant item IDs') and the consequence of omitting it, which meaningfully enriches that parameter's semantics.

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 precise verb+resource ('Read a Codex thread') and immediately scopes it against the write sibling by saying 'without sending anything', implicitly contrasting with send_to_codex_thread. It does not, however, distinguish itself from list_codex_threads, wait_codex_reply, or open_codex_thread.

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 concrete conditional guidance for the turnId parameter ('In Desktop mode, pass the exact turnId...'), which is real usage context. But it never says when to choose this tool over the other read-oriented siblings like list_codex_threads or wait_codex_reply, so alternative selection is left to inference.

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