Skip to main content
Glama

Codex bridge diagnostics

codex_status
Read-onlyIdempotent

Check the Codex setup before running calls: verify version, login status, Windows sandbox configuration, and session location, and flag when a newer agent-intern release is available.

Instructions

Check the Codex setup. Spends no quota; run it first when a call says "not found". Its bridge version row says when a newer agent-intern release is out: if so, tell the user. Also checks codex's version, whether you're logged in (codex login status, no model call), whether a Windows sandbox is configured (without one, workspace-write runs read-only), and where codex keeps its sessions.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.12.2

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, it discloses that the check consumes no quota and that login status is inspected without a model call. It also explains a meaningful operational consequence: without a Windows sandbox, workspace-write runs read-only. These details are consistent with the supplied annotations.

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 opening front-loads the purpose, zero quota cost, and primary troubleshooting trigger. The remaining text compactly explains the update-notification duty and enumerates the checks, with useful technical parentheticals and no filler.

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 zero-argument diagnostic tool, the description covers its purpose, when to run it, cost, major checks, and the operational meaning of the sandbox and version results. Because an output schema is present, exact result fields need not be repeated; the description instead supplies the interpretation and follow-up behavior an agent needs.

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?

The tool has no parameters, so there is no argument syntax or parameter behavior for the description to clarify. The baseline score of 4 applies, and the description adequately presents it as a standalone diagnostic invocation.

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?

It pairs a concrete verb and resource, "Check the Codex setup," with specific diagnostics: bridge and Codex versions, login state, Windows sandbox configuration, and session location. The explicit "no model call" wording also distinguishes it from codex_ask and codex_continue rather than leaving the broad term "status" ambiguous.

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

Usage Guidelines4/5

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

It gives an explicit trigger—"run it first when a call says 'not found'"—and notes that it spends no quota, supporting its use as a preliminary diagnostic. It also tells the agent to inform the user when a newer agent-intern release is available, but provides no explicit when-not guidance or alternative escalation path for other failures.

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