local-agent-mcp

by ezra-y

Overview Schema Source Related Servers Discussions Admin

Python

Local

Get local Codex turn status

get_codex_turn_status

Read-onlyIdempotent

Retrieve the status, items, and final agent message for a specific Codex turn using its thread and turn identifiers.

Instructions

Get status, items, and final agent message for one Codex turn.

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": {
      "thread_id": "<thread_id>",
      "turn_id": "<turn_id>"
    },
    "name": "get_codex_turn_status"
  }
}

Input Schema

Name	Required	Description	Default
`turn_id`	Yes
`thread_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Aug 24, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to restate safety. It adds the return contents (status, items, final agent message) which provides some behavioral context, but it does not disclose any edge cases or error behavior. With annotations covering safety, this is acceptable but not rich.

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 a single, front-loaded sentence with no wasted words. It states exactly what the tool does and what it returns, making it easy to scan quickly.

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

Completeness5/5

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

For a simple read-only getter with an output schema present, the description is complete. It lists the key return elements and is consistent with the annotations. No additional information is needed for an agent to call this tool correctly.

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?

With 0% schema description coverage, the description must compensate for parameter explanation. It does not explicitly define thread_id or turn_id, but the phrase 'for one Codex turn' gives context that these IDs identify the turn. The parameter names are self-explanatory, providing baseline understanding, but no additional detail or format is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the specific resource: 'status, items, and final agent message for one Codex turn.' This distinguishes it from sibling tools like get_codex_job (which operates at the job level) and list_codex_threads (which lists threads). The scope is unambiguous.

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 implies usage when you need turn-level status, but it does not explicitly state when to use this tool versus alternatives like get_codex_job or read_codex_thread. No exclusions or conditions are provided, so an agent is left to infer the appropriate context.

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