Skip to main content
Glama

Ellimist

VaR / CVaR risk attestation

quantum_risk_var_cvar
Read-only

Use this to compute Value-at-Risk and CVaR (expected shortfall) with confidence intervals for your portfolio returns, returned as a signed attestation a lender or counterparty can verify. Price: $0.05 USDC per call via x402 (no account). Not charged if it fails.

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": "quantum_risk_var_cvar"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsNo
qubitsNo
backendNoaer
returnsNoT x N periodic returns
weightsNodefaults to equal weight
confidenceNo
covarianceNo
backend_noteNoset by Ellimist; leave empty
horizon_daysNo
portfolio_valueNo
expected_returnsNo
periods_per_yearNo
requested_backendNoset by Ellimist; leave empty

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds genuinely new behavior: pay-per-call pricing ($0.05 USDC via x402), no account required, and no charge on failure, plus that the result is a signed attestation verifiable by a counterparty. It still omits compute cost/latency implications of the quantum backend and qubit settings, 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.

Conciseness4/5

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

Three tight sentences: purpose first, then pricing/auth, then billing-on-failure. Every clause carries information, though the 'with confidence intervals' phrasing is slightly ambiguous about what interval is reported.

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

Completeness3/5

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

For a 13-parameter financial computation with no output schema, the description covers purpose, cost, and output verifiability, which is the essential core. It leaves gaps on backend selection semantics and input conventions (return periodicity, units, covariance alternative), which an agent calling this tool would likely need.

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

Parameters2/5

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

With 13 parameters and only 31% schema description coverage, the description needed to carry meaning, but it only gestures at returns, confidence, and portfolio value. It says nothing about qubits/backend tradeoffs, horizon_days, periods_per_year, covariance vs. returns inputs, or the 'leave empty' fields, leaving most parameters ambiguous.

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 verb (compute) and precise resources (Value-at-Risk and CVaR/expected shortfall) for portfolio returns, plus the distinctive output form (a signed, verifiable attestation). This clearly separates it from sibling tools like quantum_portfolio_optimize or quantum_exposure_index.

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

Usage Guidelines4/5

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

Opens with an explicit trigger: 'Use this to compute VaR and CVaR ... for your portfolio returns,' which tells the agent the situation that selects this tool. It does not name when to prefer a sibling (e.g., optimizer vs. risk measure) or note exclusions, so it stops short of full routing guidance.

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