Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
cwdNoCLI option --cwd: default working directory used when discussion_start.cwd is omitted. Recommended to pass an absolute project path.
codex-argNoCLI option --codex-arg: repeatable argument that replaces the default app-server launch arguments. Values starting with '-' must be joined with '='.
codex-commandNoCLI option --codex-command: absolute path to the Codex executable, overriding CODEX_DISCUSSION_CODEX_PATH.
CODEX_DISCUSSION_CODEX_PATHNoAbsolute path to the Codex executable. Used when --codex-command is not provided; otherwise falls back to `codex` on PATH.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
models_listA

Call first to fetch the current Codex model catalog with descriptions, default model, default effort and supported effort descriptions. No inference is run. Catalog entries do not guarantee account/provider inference access.

discussion_startA

Start an independent read-only Codex conversation. Call models_list first, then select model and effort for the question complexity. Supply the question, relevant context and optional absolute project cwd. Returns discussionId and turnId immediately; read output using discussion_read.

discussion_replyA

Send a follow-up, objection or additional evidence to an existing discussion. Finish or cancel the active turn first. Model and effort can change on each reply. Omitted choices inherit; changing model without effort uses the new model default. Returns immediately; use discussion_read.

discussion_readA

Read the latest or specified turn. Poll with waitMs up to 20000 until completed, failed, interrupted or connectionLost; new output can return before completion. Follow nextCursor for more message chunks. During generation, read again without a cursor for updated text. Persisted historical per-turn model/effort may be unavailable; threadDefaults are reported separately.

discussion_cancelA

Request interruption of exactly the specified turn. An accepted cancellation request is distinct from the final interrupted status; confirm with discussion_read. Completed older turns are returned without interrupting newer work.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct lifecycle role: model catalog, starting a new conversation, replying to an existing one, reading/polling output, and cancelling a specific turn. The start-vs-reply boundary is well clarified by 'independent' new conversation versus 'existing discussion', so misselection is unlikely.

Naming Consistency5/5

All names are snake_case and follow a predictable resource_action pattern: models_list, discussion_start, discussion_reply, discussion_read, discussion_cancel. The only minor variation is plural 'models' versus singular 'discussion', which is natural and still consistent.

Tool Count5/5

Five tools map directly to the necessary catalog lookup plus discussion lifecycle operations. There is no obvious bloat, and the surface is neither too thin nor too heavy for this purpose.

Completeness4/5

The core lifecycle is covered: model discovery, start, reply, read/poll, and cancel. Minor gaps exist, such as no tool to list or discover existing discussions and no explicit finish/archive/delete operation, but agents can work around these when they track discussion IDs and read turn status.