yf-decide-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODEL | Yes | 默认模型名,可被单次调用覆盖。 | |
| API_KEY | No | Bearer 凭据。不设置时请求里完全不带这个头。 | |
| BASE_URL | Yes | 端点根地址。不要带 `/v1`,服务端会自己拼 `/v1/systemone`。 | |
| TIMEOUT_MS | No | 单次请求超时,默认 30000。 |
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 |
|---|---|
| decideA | Ask one or more typed questions about a piece of context through a System One decision endpoint (POST /v1/systemone). This is a decision model, not a chat model: it does not generate prose, it answers the questions you define. Question types:
Batch independent questions in one call; questions cannot see each other's answers. The model cannot see your conversation or local files — put every fact it needs into state, and write each full judgment into instructions. Question IDs are only response keys. |
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
There is only one tool, so there is no possibility of confusing it with another tool. Its purpose is clearly stated as a typed decision endpoint rather than a chat model.
The single tool name 'decide' is a clear, concise verb that matches the server's decision-making purpose. With only one tool, there are no inconsistent naming conventions to conflict.
A single tool is appropriate for wrapping one focused decision endpoint, and the rich question-type schema keeps it from being trivial. However, the surface is very thin, with no separate discovery or utility tools.
The tool covers the core decision operations: choice, score, noul, box, and batching independent questions. Minor gaps exist around endpoint discovery, health checks, or model metadata, but the main decision workflow is complete.