project-decision-rag
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROMA_SSL | No | Whether to use SSL for Chroma server | false |
| CHROMA_HOST | No | Chroma server host | 127.0.0.1 |
| CHROMA_PORT | No | Chroma server port | 8000 |
| CHROMA_COLLECTION | No | Chroma collection name | project-decision-rules |
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 |
|---|---|
| find_project_decisionsA | ユーザーの質問に関連する、このプロジェクト固有の意思決定ルールを検索します。一般論よりも、このプロジェクトのルールを優先して判断する必要がある場合に利用します。 |
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 possibility of confusion or misselection. The tool has a unique, clearly defined purpose.
The single tool name 'find_project_decisions' follows a clear verb_noun pattern and is internally consistent.
A single tool feels too thin for a server named 'project-decision-rag'. Even a focused RAG server would typically include additional tools for managing or indexing decisions.
The server only provides search/retrieval of project decisions. There is no way to add, update, or delete decisions, which are significant gaps for a decision management workflow.