Skip to main content
Glama
Sign In
codex-bridge

codex-bridge

by ndcorder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

codex_reset

Reset the conversation session to clear chat history and stats, enabling a fresh start for a new topic.

Instructions

Reset the conversation session with Codex. Clears history and stats. Use when starting a new topic.

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_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idNoSession key to clear; defaults to working_dir or the default session
working_dirNoOptional working directory used as implicit session key
all_sessionsNoIf true, clears every active session in this process

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions clearing history and stats but lacks detail on permanence, required permissions, or behavior when all_sessions is true.

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?

Two sentences, no fluff. Action and effect in first sentence, usage guidance in second. Perfectly concise and front-loaded.

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

Completeness4/5

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

Given tool simplicity and full param schema coverage, description covers purpose and usage adequately. Lacks mention of irreversibility and all_sessions behavior, but overall complete for reset operation.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. Description does not add meaning beyond schema for parameters; it does not explain session_id, working_dir, or all_sessions further.

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?

Description clearly states the verb 'reset' and the resource 'conversation session with Codex'. It distinguishes from siblings like codex_sessions and codex_stats by specifying it clears history and stats.

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?

Explicitly states when to use: 'Use when starting a new topic.' Does not mention when not to use or provide alternatives, but for a simple reset tool this is sufficient.

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