Skip to main content
Glama

codex_status

Read-onlyIdempotent

Checks installed Codex CLI, sign-in type, pending request summaries, and broker health so you can verify local coding-subagent readiness.

Instructions

Check installed Codex, sign-in type, pending request summaries and broker health.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "codex_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
requests_limitNo
requests_cursorNoPending-request cursor

Output Schema

NameRequiredDescriptionDefault
okYes
result_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description does add that it reports sign-in type and broker health — a diagnostic surface not implied by the annotations — but says nothing about cost, freshness, or whether a failure to reach the broker is surfaced as an error or a status field.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; each listed facet is meaningful. It is compact but reads as a comma list rather than a structured breakdown, which is fine for its length.

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

Completeness3/5

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

An output schema exists, so the description need not explain return values, and the facet list plus read-only annotations cover enough for a zero-required-param status call. However, the unexplained pagination parameters leave an ambiguity about whether the pending-request section is truncated by default.

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?

Schema coverage is only 50%: requests_cursor is documented in the schema, but requests_limit has no description beyond default 50 / max 200. The description mentions 'pending request summaries' but never explains that these two parameters paginate or bound that list, so the description does not compensate for the coverage gap.

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?

Specific verb ('Check') plus an enumerated set of resources: installed Codex, sign-in type, pending request summaries, broker health. This clearly distinguishes it as a diagnostic/status aggregation tool rather than a request or session manager. It stops short of naming a sibling it differs from, so it lands at 4 rather than 5.

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?

No when-to-use or when-not-to-use guidance is given. The sibling set includes codex_requests, which plausibly overlaps with the 'pending request summaries' facet, yet the description never says whether to call this for an overview versus calling the dedicated tool. The agent must infer usage from the facet list alone.

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