AllocContext
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOC_CONTEXT_CONFIG | No | Path to AllocContext YAML config | /app/config/config.yaml |
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 |
|---|---|
| get_context_bundleA | Full ContextBundle JSON: portfolio holdings, market, sentiment, macro, regime hints, and delta vs the prior saved snapshot. Optional assets filter (default BTC, ETH). Optional target_pct and band attach allocation_analysis (opt-in drift math). freshness=cached uses the local ingest DB; freshness=live runs ingest first. |
| get_market_contextA | Fused market backdrop: sentiment (Fear & Greed, Kalshi), macro events, FRED indicators, ETF flows, and market breadth. Optional assets filter (default BTC, ETH). freshness=cached uses the local ingest DB; freshness=live runs ingest first (requires ingest API keys on the host). |
| get_rebalance_planA | USD deltas and exchange-style move lines to reach a target BTC/ETH/CASH split. Requires allocation_pct, target_pct, and nav_usd. Optional band returns a band_check block alongside the plan. exchange=kraken|coinbase adjusts move wording. |
| get_portfolio_stateA | Live portfolio NAV, holdings[], and band weights from read-only exchange credentials passed in the request. Optional target_pct attaches allocation_analysis. Credentials are never stored. Supports kraken and coinbase. |
| check_allocation_bandB | Check whether BTC/ETH/CASH band weights are outside a drift band vs target_pct and return hint (within_band, consider_rebalance, etc.). All three inputs are required. For bundle drift, pass target_pct on get_context_bundle to attach allocation_analysis. |
| get_context_atC | Load a saved ContextBundle snapshot from ingest history. as_of is an ISO timestamp; match=at_or_before returns the latest snapshot on or before that time. |
| get_context_deltaA | Compare two ContextBundle snapshots and return notable_shifts. prior_as_of is required; omit current_as_of for latest live bundle. |
| check_allocation_bandsA | Evaluate allocation drift against multiple target_pct/band scenarios in one call. Each scenario needs target_pct; optional name and band (default 0.15). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| context_bundle_schema_v1 | Legacy ContextBundle JSON Schema (pre-holdings). |
| context_bundle_schema_v2 | ContextBundle JSON Schema (portfolio-first, optional allocation_analysis). |
| rebalance_hint_guide | Meaning of rebalance_hint codes in allocation_analysis. |
TDQS
Scored across 8 tools
get_context_bundle already embeds market context and a delta vs the prior snapshot, so get_market_context and get_context_delta overlap with it. check_allocation_band and check_allocation_bands differ only by plural and both assess drift, creating real selection ambiguity.
All tool names follow a consistent get_/check_ verb + noun snake_case pattern, and the resource names are generally clear. Minor deviations like get_context_at and the near-duplicate singular/plural band-check pair keep it from perfect consistency.
Eight tools is a well-scoped size for an allocation context server. Each tool maps to a recognizable need: context retrieval, market data, portfolio state, rebalance planning, drift checks, and snapshot comparison.
Core read/analyze workflows are covered: current context, market backdrop, portfolio state, rebalance plans, and allocation drift checks. However, there is no tool to list saved snapshots, which makes get_context_at and get_context_delta harder to use without external knowledge of available timestamps.