Determine the installed Codex CLI version to confirm availability and diagnose compatibility issues before running coding tasks.
Return the installed Codex CLI version.
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | Working directory for the codex process. | |
| env | No | Additional environment variables for codex. | |
| timeoutMs | No | Process timeout in milliseconds. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral transparency burden. It states the observable outcome (returning the version) but does not disclose execution details such as spawning a process, potential failures when Codex is not installed, or the output format. For a simple read-only version check 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single clear sentence with no filler. It is front-loaded with the action and object, making it immediately scannable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple version-check tool with no required parameters and a fully documented schema, the description is nearly complete. It lacks only minor context such as error behavior when the CLI is missing, but nothing essential to invoking the tool correctly is omitted.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the input schema already documents all three parameters (cwd, env, timeoutMs). The description adds no additional parameter semantics, which aligns with the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and object: 'Return the installed Codex CLI version.' This clearly distinguishes it from the sibling tools, none of which are about version reporting.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage context is implied: call this tool when you need to know the installed Codex CLI version. However, the description does not explicitly state when to use it versus alternatives or provide any exclusions, so it stops at implied guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.