Skip to main content
Glama

Mastering Financial Markets

MFM accumulation plan simulator (past data)

accumulation_plan
Read-onlyIdempotent

Simulate a past accumulation plan: a fixed amount bought at every month-end in a market basket over a past period chosen by the user, on the open data series (basket price on base 100, prices only: no dividends, costs, taxes or exchange rates). Returns the average purchase price, the value at the end and the result, and splits the purchases made when the basket price was ABOVE its bottom-up long-term part (gap > 0) from those made when it was WITHIN OR BELOW it (gap ≤ 0); months without a computed long-term part are counted apart. Same computation as /en/portfolio/accumulation-plan/. Nothing is stored. Markets: US (S&P 500 basket), EU (STOXX Europe 600 basket), JP (Japan basket), CH (Swiss basket). Past data only: it describes, it does not forecast, has no expected return and is not advice; say so to the user. Clients that only expose search and fetch: search "plan: market=US; amount=100; from=2022-01; to=2026-08".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "market": "<market>",
      "monthly_amount": "<monthly_amount>"
    },
    "name": "accumulation_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast purchase and valuation month (YYYY-MM); default: the latest month with a published basket price.
fromNoFirst purchase month (YYYY-MM); default: the first month with a published basket price.
marketYesMarket basket: US (S&P 500), EU (STOXX Europe 600), JP (Japan) or CH (Switzerland).
monthly_amountYesAmount bought at every month-end, in the basket currency (USD, EUR, JPY or CHF); no exchange-rate conversion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the definition discloses the output composition (average purchase price, end value, result), the split of purchases by whether the basket price sits above its bottom-up long-term part vs within/below it, and the separate handling of months without a computed long-term part. It also states 'Nothing is stored' and identifies the four supported baskets, so an agent knows the exact data basis before calling.

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 purpose and the gap-based purchase split are front-loaded, and each clause carries content: caveats, output fields, market list, search fallback. It is dense and semicolon-heavy, and the reference to the /en/portfolio/accumulation-plan/ page is low value for an agent, but nothing is padding.

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?

There is no output schema, and the definition compensates by naming the returned figures and how purchases are bucketed. Combined with the data caveats (prices only, no FX, no storage) and supported-market enumeration, an agent has everything needed to call it and to report results accurately.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all four parameters including formats and defaults; the description largely restates them. The one real addition is the search-string example ('plan: market=US; amount=100; from=2022-01; to=2026-08'), which maps parameter names for constrained clients, plus the reminder that amounts are in basket currency without FX conversion.

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

Purpose4/5

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

States a specific verb and resource: simulate past month-end fixed-amount purchases in a named market basket over a user-chosen period. The scope is unambiguous, but the definition never contrasts itself with sibling calculators such as long_term_calculator or portfolio_calculator, so an agent must infer the boundary itself.

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?

Clearly frames when the tool applies (past-period accumulation simulation), states hard limits (prices only, no dividends/costs/taxes/FX, no stored state) and instructs the agent to tell the user it is not a forecast or advice. It also provides a concrete search-string fallback for clients limited to search/fetch. It stops short of naming when another calculator would be the better choice.

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