Skip to main content
Glama

BRAINIAC Portfolio Analytics

Equal-risk-contribution and inverse-volatility weights

portfolio-analytics_risk-parity-weights
Read-onlyIdempotent

Spinu ERC (or caller risk-budget) weights and inverse-volatility weights with risk-contribution breakdown. Price $0.04 USDC. POST /api/v1/portfolio-analytics/risk-parity-weights. 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": {
      "assets": "<assets>",
      "covariance": "<covariance>"
    },
    "name": "portfolio-analytics_risk-parity-weights"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsYesassets, array. Required.
methodNomethod, string, one of erc, inverse_volatility. Required.erc
covarianceYescovariance, array. Required.
riskBudgetNoriskBudget, value. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
weightsNoweights. Array.
convergedNoconverged. Boolean.
iterationsNoiterations. Number.
limitationsNolimitations. Array.
inverseVolatilityNoinverseVolatility. Array.
riskContributionsNoriskContributions. Array.
portfolioVolatilityNoportfolioVolatility. 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 this as read-only, idempotent, open-world, and non-destructive. The description adds important behavior beyond that: it costs $0.04 USDC, uses a POST endpoint, and unpaid calls return x402 payment terms without executing.

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?

The description is three tight sentences: purpose first, then price and endpoint, then unpaid-call behavior. Every sentence adds operationally useful information without repetition.

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?

For a four-parameter analytical tool with an output schema and rich annotations, the definition covers the core computation, pricing, and payment-gating behavior. The main remaining gap is guidance on selecting between ERC and inverse-volatility methods.

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. The description adds some meaning by tying the method to Spinu ERC and inverse-volatility weights and by mentioning caller risk-budget, but it does not clarify assets or covariance semantics beyond the schema.

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?

The description names the exact output: Spinu ERC or inverse-volatility weights with a risk-contribution breakdown. It is specific about the resource and methods, but it does not explicitly distinguish this tool from nearby portfolio optimization or risk-metric siblings.

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?

The method options imply that the tool is for ERC or inverse-volatility weighting, and the description notes the payment flow for unpaid calls. However, it does not state when to choose this tool over mean-variance optimization or allocation-xray, nor when not to use it.

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