Skip to main content
Glama

calculators

by com.retirecrunch
OverviewDiscussionsAdmin

load_portfolio

Open the user's Interactive Brokers portfolio in the RetireCrunch Portfolio Rebalancer. First call the IBKR connector's get_account_positions, get_account_balances and get_account_summary, then pass their results here UNCHANGED (do not re-type or round numbers). Returns a private link that works once, for 15 minutes — give it to the user exactly as written. No login is needed because the link itself is the key: the positions are encrypted with a key that exists only in the link, and RetireCrunch's server holds just that encrypted copy, which it cannot read, for at most 15 minutes and deletes it when the link is opened. Tell the user this, and that anyone holding the link can open it once, so it should not be shared. RetireCrunch does not recommend instruments or allocations: the user sets their own targets on the page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryNoThe result of IBKR get_account_summary, unchanged (base currency + net liquidation, used to check the numbers add up).
balancesNoThe `balances` array from IBKR get_account_balances, unchanged (gives per-currency cash).
languageNoSite language for the link, matching the user's language when possible.en
positionsYesThe `positions` array from IBKR get_account_positions, unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / balances / items / additionalProperties
      Previous value: -trueNew value: +{}
    • changedInput schema / properties / positions / items / additionalProperties
      Previous value: -trueNew value: +{}
    • addedInput schema / properties / positions / items / properties / contract_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / positions / items / properties / contract_id / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / summary / additionalProperties
      Previous value: -trueNew value: +{}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the single-use 15-minute link, the no-login encryption model, server-side retention and deletion on open, the share-at-your-own-risk caveat, and that RetireCrunch gives no allocation advice. This is unusually thorough behavioral disclosure for a mutation-like tool.

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?

Front-loaded with the purpose, then sequencing, then return-value semantics. Every sentence carries an instruction or a disclosure the agent must convey to the user, though the paragraph is dense and could be trimmed slightly without losing meaning.

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?

No output schema exists, and the description compensates by explaining exactly what is returned (a private one-time 15-minute link) and how to hand it to the user. Combined with the 100%-covered input schema and the explicit prerequisite tools, nothing needed to call this correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by requiring the IBKR payloads be passed through verbatim with no rounding or retyping. It does not add syntax detail for language or the summary object, so it falls short of 5.

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?

States a precise verb and resource: opens the user's Interactive Brokers portfolio in the RetireCrunch Portfolio Rebalancer. This clearly separates it from rebalance_portfolio and get_rebalance_plan, which operate on already-loaded portfolios.

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

Usage Guidelines5/5

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

Explicitly names the prerequisite tools (get_account_positions, get_account_balances, get_account_summary) and the required call order, plus a concrete prohibition: pass results UNCHANGED, do not re-type or round numbers. An agent knows exactly what to do before calling this.

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

All calculators toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources