Skip to main content
Glama

rebalance_check

Read-onlyIdempotent

Analyze current portfolio and suggest trades to rebalance toward target allocation. Supports multiple modes including total rebalance, threshold bands, and cash allocation strategies.

Instructions

Buy/sell/hold suggestions to move current holdings toward the target allocation (ASSET_TARGET). There are exactly 4 modes: 'to_total' (rebalance the whole book back to target weights — ALSO deploys new_cash into the rebalance if you pass it) and 'bands' (trade only sleeves that drifted past the 5%/25% threshold — the one mode that IGNORES new_cash); 'fixed_dca' (spread new_cash across the target mix) and 'cash_flow_only' (put new_cash into the most-underweight sleeves) — these two REQUIRE new_cash > 0 and suggest all-HOLD when it is 0. Offline + read-only — it suggests, never trades. A NEW target ticker can't be sized offline (no cached price); those appear under 'unpriced'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoto_total
new_cashNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
asofYes
modeYes
noteNoRead-only: figures are derived from your transaction log and the on-disk price cache. Uncached prices are fetched online on demand — a one-time core warm on the first cold call, plus any new ticker you ask about (set ASSET_MCP_OFFLINE=1 to keep it strictly offline); a value still unavailable shows null (n/a), never a guess. This is a view, not financial advice.
new_cashNonew cash deployed this run: fixed_dca / cash_flow_only REQUIRE it, to_total also deploys it if passed, only bands ignores it. For fixed_dca / cash_flow_only, 0 → all-HOLD.
unpricedYesheld/target tickers with no cached price; offline, a NEW target ticker can't be sized — run the CLI online for a full plan
suggestionsYes
target_sourceNothe ASSET_TARGET file the plan is measured against
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and idempotentHint. The description adds that it only suggests trades, never executes, and mentions edge cases like unpriced tickers. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is information-dense but somewhat long. It clearly maps modes and behaviors, though a more structured formatting (e.g., bullet points) could improve readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (4 modes, 2 parameters, output schema present), the description covers behavioral details, edge cases, and mode-specific rules comprehensively. The output schema handles return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description fully explains the modes and the role of new_cash in each mode, including default behavior (all-HOLD when new_cash=0 for two modes). This adds crucial meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states it provides buy/sell/hold suggestions to rebalance toward target allocation, and lists all four modes. This clearly distinguishes it from sibling tools like portfolio_summary or propose_allocation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use each mode (e.g., 'bands' ignores new_cash, 'fixed_dca' requires new_cash > 0) and notes that the tool is offline and read-only. However, it doesn't explicitly compare to sibling tools or state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/disin7c9/asset-management'

If you have feedback or need assistance with the MCP directory API, please join our Discord server