Vintage
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRED_API_KEY | No | Free API key from FRED to unlock 800k macro series with first-release vintages. | |
| VINTAGE_CACHE_DIR | No | Directory for cache. Defaults to ~/.cache/vintage. | ~/.cache/vintage |
| VINTAGE_USER_AGENT | No | User agent string for SEC EDGAR. Example: "Your Name your@email.com". |
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 |
|---|---|
| capabilitiesA | Everything Vintage can answer, with the arguments each field needs. Call this first. It returns every field prefix, whether it needs an
|
| resolveA | Turn any identifier into the entity key every other verb accepts. Accepts a ticker ("AAPL"), a CIK ("CIK0000320193" or "320193"), a FRED series id, or a French dataset name. Start here when unsure what an entity is called. |
| discoverA | Search every source's catalog for fields matching a plain-English query. This is how breadth is reached. There is no per-source tool. With
|
| fetchA | Fetch any field from any source, as point-in-time rows. Field forms: "us-gaap:Assets" (needs entity), "price:close" (needs entity), "fred:CPIAUCSL", "french:ff3", "openap:Mom12m" (or "openap:*" for all 331 published claims), "crypto:close" (needs an entity like BTC-USD), "short:short_ratio" (needs an entity), "ape:all-stocks", "13f:value" (needs a manager like BERKSHIRE), "bls:CUUR0000SA0", "bea:T10101". Run discover first if unsure.
|
| eventsA | Timeline of what happened to an entity, with exact public timestamps. Currently the SEC filing stream, 8-K material events, 10-K/10-Q, Form 4 insider transactions, 13D/G stakes. Every row carries the minute it became public, which is what makes event studies possible. |
| backtestA | Run a cross-sectional backtest. Point-in-time and costed by construction. At each rebalance the engine sees only data knowable strictly before that date. Costs are always charged on turnover; there is no zero-cost mode. The Signals: momentum_12_1, momentum_6_1, reversal_1m, low_volatility, trend_200d. |
| benchmarkA | Score a backtest against the published Fama-French factors. Answers the question that decides whether a result is interesting: did you discover something, or rebuild a factor that has been public since 1993? Datasets: ff3, ff5, momentum, ff3_daily, industry49. |
| statusA | Cache size, configured keys, sources available, and specs tried so far. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| capabilities_resource | The same surface as the `capabilities` tool, for clients that preload resources instead of spending a tool call on orientation. |
TDQS
Scored across 8 tools
Each tool serves a unique, clearly delineated role: capabilities for introspection, resolve for entity mapping, discover for field search, fetch for data retrieval, events for timeline data, backtest for running strategies, benchmark for performance comparison, and status for system health. No two tools overlap in their core function.
All tool names are single lowercase words (capabilities, resolve, discover, fetch, events, backtest, benchmark, status), following a minimal and uniform naming convention with no mixing of styles such as underscores or camelCase.
8 tools provide a well-scoped interface for quantitative finance research, covering the full workflow from exploration to validation without unnecessary redundancy or excessive granularity.
The set provides a complete lifecycle: capabilities and discover facilitate exploration, resolve handles entity identification, fetch retrieves data, events offers time-series events, backtest tests strategies, benchmark compares against factors, and status monitors the system. There are no evident gaps for the stated purpose.