mcp-server-decisions
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DECISIONS_LOG_PATH | No | Path to the decision log file. By default, the server writes to ~/.local/share/mcp-decisions/decisions_log.json. Set this environment variable to use another file. | ~/.local/share/mcp-decisions/decisions_log.json |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| record-decisionB | Register a technical decision with problem, solution, alternatives, and technologies |
| record-predictionA | Register a measurable prediction linked to a decision |
| record-outcomeA | Close the prediction loop: record actual results and calculate accuracy |
| query-decisionsA | Search prior decisions by keyword, technology, or domain |
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 4 tools
Each tool has a clearly distinct purpose: querying decisions, recording a decision, recording a prediction for that decision, and recording the outcome. There is no overlap or ambiguity.
All tool names follow the same pattern: a verb followed by a noun, using lowercase and hyphens (e.g., record-decision). The naming is perfectly consistent.
Four tools cover the core workflow of managing decisions with predictions and outcomes. The count is appropriate for this focused domain, not too few or too many.
The tool set covers the main lifecycle: querying, recording decisions, adding predictions, and logging outcomes. Missing update or delete functionality, but the core workflow is complete.