Fortunest demo

Risk summary

risk

Read-onlyIdempotent

DEMO portfolio (synthetic, shared, read-only). Read the portfolio's risk picture in selectable pieces instead of the whole context. include (default ['metrics']) ⊆ metrics, drawdown, correlations, diversification, benchmarks, fxAttribution, fingerprint. metrics = volatility, Sharpe, Sortino, max and current drawdown, best and worst day, plus the note on what the per-holding risk figures mean. drawdown = the max drawdown's peak, trough, recovery and length, and the current one. correlations = the strongest pairs, strongest absolute correlation first, with the effective number of independent bets. diversification = the 0-100 score, its grade, the sub-scores and the card's own takeaways. benchmarks = one row per selected benchmark with its own return and the portfolio's beta and correlation to it. fxAttribution = how much of the return came from the currencies rather than from the assets. fingerprint = the Portfolio Fingerprint card: six axes (value, growth, past, health, income, diversification) scored 0-6 by fixed pass/fail checks, each with its measured value, threshold and coverage, plus the card's one-line verdict. range (all | 1y, default all) applies to the ratio metrics only — 1y gives the trailing-year volatility, Sharpe and Sortino plus the rolling 12-month envelope, while drawdowns, correlations and diversification are always whole-history. UNITS: volatility, maxDrawdown, currentDrawdown, correlation and the daily returns bestDay.ret and worstDay.ret are FRACTIONS (0.18 = 18%); a field ending in Pct is a percent. Statistics of the user's own history; never investment advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "risk"
  }
}

Input Schema

Name	Required	Description	Default
`range`	No
`include`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that the portfolio is synthetic, shared, and read-only; that `range` applies only to ratio metrics while drawdowns, correlations, and diversification are whole-history; and that values use fractional versus percent units. These are meaningful behavioral constraints that reduce misuse risk.

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 description is front-loaded with purpose and then systematically covers each option, so most content earns its place. It is dense and somewhat run-on, but the length is justified by the seven selectable sections and unit caveats.

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?

With no output schema and no schema parameter descriptions, the description supplies enough detail about each returnable section, defaults, range behavior, and units for an agent to invoke the tool correctly. The annotations cover safety, and the description covers the remaining operational context.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it does: it lists every `include` value, explains each returned section, gives the default, and explains the `range` enum and its limited scope. It also clarifies unit conventions for the returned fields.

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 states a specific verb and resource: reading the portfolio's risk picture in selectable pieces. It clearly defines what this tool returns, but it does not explicitly differentiate itself from named siblings such as allocation, warnings, or get_trade_plan.

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 through the selectable `include` sections and the default to `metrics`, but there is no explicit when-to-use or when-not-to-use guidance versus alternatives. An agent can infer that this is the risk-summary endpoint, but routing guidance is thin.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fortunest demo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.