Skip to main content
Glama

BRAINIAC Portfolio Analytics

Monte Carlo retirement or savings goal

portfolio-analytics_monte-carlo-goal
Read-onlyIdempotent

Project a contribution/withdrawal plan with mulberry32 Monte Carlo paths and report success probability and terminal wealth percentiles. Price $0.05 USDC. POST /api/v1/portfolio-analytics/monte-carlo-goal. An unpaid call returns the x402 payment terms and does not run.

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": {
      "startValue": "<startValue>",
      "years": "<years>",
      "meanReturn": "<meanReturn>",
      "volatility": "<volatility>"
    },
    "name": "portfolio-analytics_monte-carlo-goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoseed, integer, from -9007199254740991 to 9007199254740991. Required.
pathsNopaths, integer, from 100 to 100000. Required.
yearsYesyears, integer, from 1 to 100. Required.
timingNotiming, string, one of start, end. Required.start
inflationNoinflation, number, from 0 to any. Required.
meanReturnYesmeanReturn, number. Required.
startValueYesstartValue, number. Required.
volatilityYesvolatility, number, from 0 to any. Required.
percentilesNopercentiles, array. Required.
annualWithdrawalNoannualWithdrawal, number, from 0 to any. Required.
annualContributionNoannualContribution, number. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
limitationsNolimitations. Array.
successProbabilityNosuccessProbability. Number.
medianDepletionYearNomedianDepletionYear. Number.
terminalPercentilesNoterminalPercentiles. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the description's added value is the pricing ($0.05 USDC), the endpoint path, and the crucial x402 behavior that an unpaid call returns payment terms and does not execute. That is genuine behavioral context beyond the annotations; it does not cover error modes or rate limits, so not a 5.

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

Conciseness5/5

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

Three tight sentences, front-loaded with what is computed, followed by cost and transport details. Every sentence carries information an agent needs; nothing is redundant.

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

Completeness4/5

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

With 11 parameters, full schema coverage, an output schema, and annotations, the description supplies the critical payment and execution semantics. It leaves the financial interpretation of 'success probability' (goal threshold vs depletion) unstated, which is a modest gap for an 11-parameter financial tool.

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 description coverage is 100%, so the schema already documents every parameter including ranges, defaults, and the timing enum. The description adds meaning for seed determinism ('mulberry32') and ties annualContribution/annualWithdrawal to the plan narrative, but gives no syntax or interaction guidance beyond that, so the baseline 3 holds.

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: projects a contribution/withdrawal plan via Monte Carlo and reports success probability plus terminal wealth percentiles. It is clearly distinct from sibling analytical tools like stress-test or fee-drag-project, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by 'retirement or savings goal' projection, and the payment precondition is spelled out, but there is no explicit when-to-use versus alternatives such as stress-test or var-cvar, and no exclusion criteria.

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