futures-kb
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FUTURES_KB_DB | No | SQLite database path | data/futures_kb.sqlite3 |
| FUTURES_KB_API_KEY | No | API key required for HTTP write and report endpoints if set | |
| FUTURES_KB_RAW_DIR | No | Crawler raw output directory | data/raw |
| FUTURES_KB_API_HOST | No | API listen address | 127.0.0.1 |
| FUTURES_KB_API_PORT | No | API listen port | 8787 |
| FUTURES_KB_CRAWLER_CONFIG | No | Crawler whitelist config path | config/crawlers.local.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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| daily_report_contextB | Return one compact computed packet for SH, V, and JM. This is the only market payload that should enter the report context. |
| manual_data_submitA | Validate and upsert structured spot, inventory, operating-rate, or other daily metrics. The tool returns counts only, not the submitted dataset. |
| market_run_crawlerB | Run the configured native crawler or FuturesIntelTool refresh for one supported symbol and date. Only run status is returned. |
| report_saveB | Persist a completed report outside model context. Re-saving the same date, type, title, and source updates the existing report. |
| report_listA | Return compact report metadata and short summaries only. Use this before reading any past report; full report content is never returned. |
| report_readB | Read one selected report with a token budget. Use next_offset to continue only when necessary. |
| research_searchB | Search FuturesIntelTool or native news, announcements, and research notes. Returns at most three short excerpts with citations. |
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 7 tools
Each tool has a clearly distinct responsibility: market context generation, manual data submission, crawler execution, report persistence, report listing, report reading, and research search. There is no meaningful overlap or ambiguity between tool purposes.
The report_* tools follow a noun-verb pattern (save/list/read), and manual_data_submit is similar, but daily_report_context, market_run_crawler, and research_search do not follow the same convention. This mixed structure makes the naming pattern less predictable.
Seven tools is a well-scoped size for a futures knowledge base server, covering data ingestion, crawling, reporting, and research without unnecessary bloat. Each tool contributes a distinct capability.
The tool set covers the main workflow: submit/ingest data, generate report context, save/list/read reports, and search research. Minor gaps exist, such as no direct way to query or delete submitted data and no explicit report deletion, but the core lifecycle is otherwise supported.