Skip to main content
Glama

help

Get help information for the Codex CLI to assist with code analysis, generation, and refactoring tasks.

Instructions

Get Codex CLI help information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler class for the 'help' tool, which executes 'codex --help' and returns the output.
    export class HelpToolHandler {
      async execute(args: unknown): Promise<ToolResult> {
        try {
          HelpToolSchema.parse(args);
    
          const result = await executeCommand('codex', ['--help']);
    
          return {
            content: [
              {
                type: 'text',
                text: result.stdout || 'No help information available',
              },
            ],
          };
        } catch (error) {
          if (error instanceof ZodError) {
            throw new ValidationError(TOOLS.HELP, error.message);
          }
          throw new ToolExecutionError(
            TOOLS.HELP,
            'Failed to execute help command',
            error
          );
        }
      }
    }
  • The Zod schema definition for the 'help' tool inputs (currently empty object).
    export const HelpToolSchema = z.object({});
  • The registration of the HelpToolHandler in the toolHandlers registry.
    [TOOLS.HELP]: new HelpToolHandler(),
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states what the tool does ('Get help information') but doesn't describe behavioral traits such as output format, error handling, or any constraints. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 description is a single, efficient sentence with zero waste. It's front-loaded with the core purpose and uses minimal words to convey the essential information. Every word earns its place, making it highly concise and well-structured.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It states the purpose but lacks details on behavioral aspects like what the help information includes or how it's formatted. For a help tool, more context on output expectations would improve completeness.

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 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The description appropriately doesn't mention parameters, which is correct for a no-parameter tool. It adds no semantic value beyond the schema, but that's acceptable here.

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?

The description 'Get Codex CLI help information' clearly states the action ('Get') and resource ('Codex CLI help information'), making the purpose immediately understandable. It's specific enough to distinguish it from siblings like 'codex', 'listSessions', and 'ping', though it doesn't explicitly differentiate from them. The verb 'Get' is appropriate for a help retrieval operation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context for usage, or comparisons to sibling tools. While the purpose is clear, the lack of usage instructions leaves the agent without direction on optimal invocation timing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tom-wahl/codex-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server