Skip to main content
Glama

codex_get

Read-onlyIdempotent

Read task state, usage, and ownership claims, page pending requests, and fetch scoped result or artifact evidence by id. Use views, offset, and limit to inspect reconciliation and permission receipts.

Instructions

Read task state and cumulative usage. workspace_claims explain ownership; page requests, children and claims. Large fields identify truncated_fields. result pages turn evidence (pin result_id); artifact reads scoped bytes by artifact_id. Use offset/limit. reconciliation explains recovery; permissions pages receipts and scope.

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": {
      "task_id": "<task_id>"
    },
    "name": "codex_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoDetail or compact supervision viewdefault
limitNo
offsetNo
task_idYesTask id
turn_idNo
result_idNo
artifact_idNo
claims_limitNo
claims_offsetNo
requests_limitNo
requests_cursorNoPending-request cursor
subagents_limitNo
subagents_offsetNo

Output Schema

NameRequiredDescriptionDefault
okYes
result_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description does add genuine context beyond that: truncated_fields marks cut-off data, result pages pin a result_id as evidence, and artifact reads are byte-scoped by artifact_id. That value is real but is delivered in compressed jargon ('scoped bytes', 'turn evidence') that an agent must reverse-engineer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and the scoping statement is front-loaded, so it is not padded. However, the semicolon-chained sentence fragments have no clear hierarchy, forcing the reader to parse cryptic clauses rather than skim a structured list of capabilities.

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?

An output schema exists, so return values need not be explained, but with a required task_id plus 12 optional paging/selector parameters the definition leaves too much undescribed. Key selectors such as view and turn_id and the three distinct pagination families are not made usable from the description alone.

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

Parameters2/5

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

With 13 parameters and only 23% schema description coverage, the description must carry the load and largely does not. It never explains the view enum meanings or turn_id, and 'page requests, children and claims' only loosely maps to requests_limit/requests_cursor, subagents_limit/subagents_offset and claims_limit/claims_offset without naming them.

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

Purpose3/5

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

The opening sentence 'Read task state and cumulative usage' gives a specific verb and resource, but the remaining clauses are telegraphic fragments ('result pages turn evidence (pin result_id)', 'reconciliation explains recovery') that obscure what the tool actually returns. It never distinguishes itself from plausible siblings like codex_status, codex_requests, codex_subagents or codex_usage that appear to cover overlapping surface.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use offset/limit' is an invocation instruction, not a when-to-use rule. No guidance is given on which of the six views to select or when this tool should be preferred over the sibling tools that clearly overlap with it.

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