Skip to main content
Glama

BRAINIAC Portfolio Analytics

Scenario stress test on holdings

portfolio-analytics_stress-test
Read-onlyIdempotent

Apply caller-defined asset-class, factor and rate shocks to holdings and report P/L by holding and in total. Price $0.03 USDC. POST /api/v1/portfolio-analytics/stress-test. 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": {
      "holdings": "<holdings>",
      "scenarios": "<scenarios>"
    },
    "name": "portfolio-analytics_stress-test"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdingsYesholdings, array. Required.
scenariosYesscenarios, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
scenariosNoscenarios. Array.
limitationsNolimitations. Array.

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 and openWorld, so the safety profile is covered. The description adds genuinely new behavioral facts the annotations cannot express: a $0.03 USDC price and the fact that an unpaid call returns x402 payment terms without executing. That payment-failure branch is exactly the kind of context an agent needs 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.

Conciseness5/5

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

Three short sentences, front-loaded with the action and output, then price, then endpoint, then the payment edge case. No filler and nothing repeated from the schema.

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?

An output schema exists and annotations cover safety, so the description need not explain return values. It covers the pricing gate, which is a real completeness win. The remaining gap is that it does not hint at how the nested holdings attributes interact with the rate shock, which matters for a two-required-parameter tool with non-trivial nested payloads.

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 baseline is 3. The description's 'asset-class, factor and rate shocks' phrase loosely maps to assetClassShocks, factorShocks and rateShockBp, which adds a little meaning, but it says nothing about the holdings item fields (betas, mapping, duration, convexity) or how shocks combine. The schema carries the load.

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: apply caller-defined asset-class, factor and rate shocks to holdings and report P/L per holding and in total. That is concrete enough to separate it from risk-metrics or var-cvar. It stops short of naming which sibling to use when the caller wants a probabilistic rather than deterministic shock, so it is clear but not fully differentiated.

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 'caller-defined' shocks, which tells the agent the scenarios are supplied rather than generated, but there is no explicit when-to-use versus var-cvar or monte-carlo-goal. It also gives no prerequisites for the holdings payload (e.g. duration/convexity needed for the rate shock to matter). Adequate but leaves routing 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