Portfolio-aware crypto context — CEX or wallet holdings, holdings-scoped market, optional allocation analysis
9 tools with complete JSON schemas and descriptions. Naming is verb-forward and clear (get_*, check_*). Descriptions are substantive (100-250 chars avg), explaining WHAT and WHEN. Parameters are well-typed with enums for constrained inputs (scope, freshness, match, exchange). However, output schemas are NOT documented, LLMs cannot see what fields to expect in responses. Error handling is absent from visible code; no recovery guidance or categorization. Security is strong (no secrets in params, read-only risk classification), but composition could be tighter, several tools overlap (get_context_bundle vs get_market_context vs get_context_at). Parameter descriptions lack examples of valid enum values inline.
Evaluate allocation drift against band width (default 0.15 = 15%).
Evaluate multiple allocation scenarios against band widths.
Get context at a specific timestamp with optional asset filtering and allocation analysis.
Return the full deterministic context bundle for daily or weekly scope.
Get context delta between two timestamps with optional asset filtering.
Score local theses without returning the full ContextBundle.
Return ContextBundle subset for daily or weekly scope.
Output schemas not documented. LLMs cannot see what fields (e.g., allocation_analysis, expectation_review, market_data) are returned or their types. This forces agents to guess structure and risks parsing failures.
No error handling or recovery guidance visible. Tools lack categorization of errors as retryable, user-fixable, or fatal. No actionable error messages (e.g., 'portfolio_not_configured' setup blocks exist in setup.py but are not integrated into tool responses).
Overlapping tool responsibilities. get_context_bundle, get_market_context, and get_context_at all return market/context data with different filtering. LLMs must reason about which to call; composition could be tighter.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
Fetch live portfolio from exchange keys or a public EVM wallet address.
Compute rebalance plan from current allocation and NAV.
Enum values not shown in parameter descriptions. 'scope' accepts 'daily' or 'weekly', 'freshness' accepts 'cached' or 'live', but descriptions do not list valid options inline. LLMs must infer from schema.
Parameter 'api_key' and 'api_secret' in get_portfolio_state are marked as never stored, but passing credentials as parameters is a security anti-pattern. Should use server-side secret injection or environment variables only.