codex-code-review
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| review_uncommitted_changesB | Run Codex review on uncommitted changes using the app-server review API. Returns structured results for each run. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no ambiguity. The agent will always select the same tool for the server's purpose.
The single tool name follows a clear verb_noun pattern (review_uncommitted_changes), but consistency cannot be fully assessed with only one tool.
A single tool is very thin for a server. While it may serve a narrow purpose, it feels incomplete and limits the server's usefulness.
The tool only covers reviewing uncommitted changes. Obvious gaps include reviewing committed changes, specific files, or providing review history.