Skip to main content
Glama

Preview changes to an account

preview_simulation
Read-onlyIdempotent

Measure an account as it is and after changes, without saving anything.

Answers which way the client's position would move, and by how much. The account
is measured twice through the Risk tab's own pane. ``save_simulation`` takes the
same changes and saves them for the dashboard to compare.

One form per call. ``strategy_id`` + ``amount`` buys a strategy. ``changes`` are
several signed changes at once (a switch is a negative amount on an account plus
an equal positive one; an account cannot be reduced below what it holds). A
change with ``asset_id`` is one instrument: "sell 20,000 of Volvo in the ISK and
buy Investor" is ``{id: ISK, asset_id: Volvo, amount: -20000}`` plus
``{asset_id: Investor, amount: 20000}`` with ``account_id: ISK``; for a switch
between instruments that names one account, that account is the default.
``weights`` with ``account_id`` reweights one account at its current value: each
weight is an instrument's share of it, and held instruments left out are sold.
Weights adding up to 1 stay fully invested; less holds the rest as cash; more,
up to 2, borrows the excess as cash. Instrument weights from
``solve_equity_weights`` or ``solve_allocation_weights`` fit as they are.
Otherwise ``account_id`` defaults to everything the client holds, or everything
one client holds with ``person_id``. An empty account is valid for the first two
forms: the before side is empty.

Nothing is written. There is no track record for a simulation and the returns
tab is unavailable for it. The result is a measurement, not a suitability
judgement; the client's own limits are not read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "preview_simulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNo
changesNo
weightsNo
person_idNoThe id of one person, family or entity this login holds. Omit for everything this login holds.
account_idNo
strategy_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description still adds real value beyond that: 'Nothing is written,' no track record, returns tab unavailable, and that the result is a measurement not a suitability judgement with client limits unread. These are useful behavioral caveats, though the core no-write claim largely restates the annotations.

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 core purpose and the no-save guarantee, then organized by form. It is dense and long, but nearly every sentence carries operational detail (defaults, edge cases, worked example) rather than filler.

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?

For a 6-parameter, no-output-schema tool with three distinct call forms, the description covers defaults, empty-account validity, weight arithmetic, and the measurement-vs-judgement distinction. Nothing an agent needs to invoke it correctly appears missing.

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?

Schema coverage is only 17%, so the description must compensate, and it does: it explains strategy_id+amount, the signed-change semantics of changes (switch = negative plus equal positive, account cannot go below holdings), the asset_id single-instrument case with a worked example, and the weights semantics including sum-to-1/less/more-up-to-2 borrowing rules. This adds substantial 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?

States a specific verb and resource ('Measure an account as it is and after changes, without saving anything') and explicitly contrasts with the sibling save_simulation, which 'takes the same changes and saves them.' An agent can distinguish the two without opening either schema.

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 enumerates the three call forms (strategy_id+amount, changes, weights) and the conditions selecting each, plus the account_id/person_id defaulting rules. It also names the alternative (save_simulation) and its difference, leaving little to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources