Skip to main content
Glama

BRAINIAC Portfolio Analytics

Time-weighted and money-weighted returns

portfolio-analytics_performance-twr-mwr
Read-onlyIdempotent

Compute linked TWR, Modified Dietz and XIRR from valuations and external cash flows, with optional annualisation. Price $0.04 USDC. POST /api/v1/portfolio-analytics/performance-twr-mwr. 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": {
      "valuations": "<valuations>"
    },
    "name": "portfolio-analytics_performance-twr-mwr"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowsNoflows, array. Required.
annualizeNoannualize, boolean. Required.
valuationsYesvaluations, array. Required.

Output Schema

NameRequiredDescriptionDefault
twrNotwr. Number.
daysNodays. Number.
xirrNoxirr. Number.
statusNostatus. String.
sourcesNosources. Array.
subPeriodsNosubPeriods. Array.
limitationsNolimitations. Array.
modifiedDietzNomodifiedDietz. Number.

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, so the bar is lower, and the description adds real context: the endpoint path, the $0.04 USDC price, and the important x402 behaviour that an unpaid call returns payment terms without executing. It stops short of noting any input constraints (e.g., valuation ordering, minimum points for XIRR convergence).

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 short clauses, metrics front-loaded, then price, then endpoint, then the payment failure mode — no filler and nothing buried.

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 an output schema present, return values need not be explained, and pricing/payment behaviour is covered. What is absent is domain guidance for a compute tool — input requirements for XIRR to converge or how cash flows are aligned to valuations — which keeps it just below complete.

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 defines date/value/amount/beforeFlow. The description only adds meaning to 'annualize' by calling annualisation optional; it says nothing about how flows interact with valuations or the role of beforeFlow, so baseline 3 applies.

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 computational verb ('Compute') plus the exact measures produced — linked TWR, Modified Dietz, XIRR — and the required inputs (valuations, external cash flows). This is instantly separable from siblings like risk-metrics, brinson-attribution or var-cvar, which answer different analytical questions.

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

Usage Guidelines2/5

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

The description never says when to pick this over a sibling analytic (e.g., when to want time-weighted vs money-weighted output, or when attribution/risk-metrics is the better call). The only conditional given concerns payment, not tool selection.

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