openai-decisions-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Your OpenAI API key. Supply it through the server environment, or put it in a private environment file outside the repository and pass `--env-file /absolute/path/credentials.env`. | |
| CLAUDE_PROJECT_DIR | No | Optional project directory used as the project root when MCP Roots are unavailable and no `--root` option is supplied. If unset, the server falls back to its startup working directory. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| decideA | Evaluate text, project files, images or PDF pages against caller-defined predicate, choice or score questions. Batch independent questions about shared evidence. Use paths instead of copying files. Returns compact answers and coverage; full=true includes all probabilities. Makes a paid OpenAI API request. |
| evaluate_batchA | Apply common typed questions independently to up to 20 named items, each containing text or file/image/PDF sources. At most 3 evaluations run concurrently. Returns per-item results/errors in input order; never replays successful items. Paid requests: one per valid item. Caller chooses the criteria and subsequent selection. |
| find_codeA | Locate relevant code within caller-supplied project files or line ranges. Evaluates every 200-line chunk with 20-line overlap, returns paths/ranges and relevance probabilities without code text. Discover candidate paths with your normal file listing first. Maximum 20 chunks and 1 MiB total text; oversized scopes fail before any paid call. One paid request per chunk, up to 3 concurrently. Returns every result, refusal and error; no automatic filtering or Read hook. Independent chunks cannot establish cross-file behavior. |
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 3 tools
find_code is clearly distinct, but decide and evaluate_batch both perform batched paid OpenAI evaluations over text/files/images/PDFs. The distinction between multiple questions on shared evidence vs. common questions across many named items is useful but subtle enough that an agent could misselect.
All names use lowercase snake_case and start with an imperative verb, giving a mostly predictable pattern. decide is a bare verb while evaluate_batch and find_code include an object noun, which is a minor inconsistency.
Three tools is compact and each covers a meaningful operation, fitting the server's focused evaluation purpose. The slight overlap between decide and evaluate_batch keeps it from being a perfectly scoped set.
The surface covers single/batched evaluation across text, files, images, PDFs, and code relevance search, which is solid for an OpenAI decision/evaluation server. Minor gaps include reliance on external file listing for code discovery and no built-in project/file inventory.