Skip to main content
Glama
Sign In
codex-computer-use-mcp

codex-computer-use-mcp

by tmustier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

js_reset

Read-only

Reset the persistent cua_repl JavaScript session to clear accumulated state and start a fresh execution context.

Instructions

Reset the persistent cua_repl JavaScript session. Computer Use is not ready: Codex app-server was not found. Checked: /Applications/ChatGPT.app/Contents/Resources/codex-cli/CodexCLI.app/Contents/MacOS/codex, /Applications/ChatGPT.app/Contents/Resources/codex, /root/Applications/ChatGPT.app/Contents/Resources/codex-cli/CodexCLI.app/Contents/MacOS/codex, /root/Applications/ChatGPT.app/Contents/Resources/codex. Install or update the official ChatGPT macOS app (https://chatgpt.com/download), then open it. If it is installed elsewhere, set "codexPath" to its absolute path in /app/config.json, or remove "codexPath" to restore automatic discovery.

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": "js_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

C2.4/5.0
Behavior1/5

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

The description says the tool resets a persistent session, which discards accumulated JS state, yet the annotations declare readOnlyHint=true and destructiveHint=false. That is a direct conflict, and the description never states what is lost (variables, imports, history) or whether the call errors when Codex is unavailable. Details about search paths and config keys do add context, but the core behavioral claim contradicts the structured hints.

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

Conciseness2/5

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

The useful content is one short sentence; everything after 'Computer Use is not ready' is a multi-line error trace with four absolute filesystem paths. It is not front-loaded toward the tool's behavior and the bulk of the text does not earn its place in a tool definition.

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?

For a zero-parameter mutation of shared session state with no output schema, the description should explain what reset clears and what the caller observes afterwards. Instead it is dominated by installation troubleshooting, leaving the actual effect of the call undocumented.

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 takes no parameters, so there is nothing for the description to disambiguate and the baseline is 4. The referenced 'codexPath' is a server config key, not an input parameter, so its mention neither helps nor hurts parameter semantics.

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 gives a specific verb and resource ('Reset the persistent cua_repl JavaScript session'), which is clear on its own. However, roughly 80% of the remaining text is an environment diagnostic about the Codex app-server not being found, which has no bearing on what the tool does and blurs the tool's purpose. There is also no differentiation from the sibling 'js' tool that presumably shares the same session.

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 guidance on when to reset versus when to just use the 'js' tool, no mention of the 'computer_use_status' sibling, and no statement of whether a reset is required after an error. The installation instructions are remediation for a broken environment, not usage guidance for the tool itself.

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

Deploy Server

Other Tools