Codex Control Plane MCP

Overview Schema Source Related Servers Discussions Admin

codex_get_chat

Recover context and inspect final reports by reading chat history from transcripts or legacy fallback.

Instructions

Read bounded chat content from hook history, transcripts, or legacy fallback. Use this for context recovery and final report inspection. It is not a write path and should not trigger retries.

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": {
      "chat_id": "<chat_id>"
    },
    "name": "codex_get_chat"
  }
}

Input Schema

Name	Required	Default
`chat_id`	Yes
`project_id`	No
`range`	No
`include_tool_calls`	No
`include_tool_outputs`	No
`include_command_outputs`	No
`include_reasoning`	No
`include_metadata`	No
`include_items`	No
`tail_max_messages`	No
`tail_max_chars`	No
`force_refresh_summary`	No
`response_budget_chars`	No
`format`	No	structured

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`agentGuidance`	No
`agentGuidanceText`	No
`recoveryAttemptState`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJun 19, 2026
- addedOutput schema / properties / agentGuidance
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
- addedOutput schema / properties / agentGuidanceText
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / recoveryAttemptState
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedv0.1.2Jun 18, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description adds some behavioral info (read-only, no retries). Yet it omits details like pagination, rate limits, or side effects. The statement 'Read bounded chat content' hints at limits but does not explain bounding 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?

The description is two sentences, each earning its place. It front-loads the core purpose and immediately adds usage guidance. No fluff or repetition.

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?

Given the tool's complexity (14 params, nested range object, many options), the description is far too sparse. It does not explain how to use the range modes, include flags, formatting, or budget parameters. The output schema exists but the description offers no guidance on interpreting results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides no explanation of any of the 14 parameters, despite 0% schema description coverage. Key parameters like chat_id, range, include_* flags, format, and budgets are completely unaddressed, forcing the agent to rely solely on parameter names and defaults.

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 tool reads bounded chat content from specific sources (hook history, transcripts, legacy fallback), and mentions use cases (context recovery, final report inspection). It distinguishes from sibling getters by specifying 'bounded chat content' rather than status or diagnostics.

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?

The description provides when to use ('context recovery', 'final report inspection') and what not to do ('not a write path', 'should not trigger retries'). However, it does not explicitly contrast with sibling tools or mention when to avoid it.

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

Deploy Server