Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_crypto_portfolio_sharpe_ratio

Calculate risk-adjusted Sharpe and Sortino ratios plus 95% Value at Risk for multi-asset crypto portfolios from expected return, volatility, and risk-free rate inputs.

Instructions

Crypto Portfolio Sharpe Ratio & Value at Risk (VaR 95%) Calculator. Calculate risk-adjusted Sharpe Ratio, downside Sortino Ratio, and 95% Parametric Value at Risk (VaR) for multi-asset cryptocurrency portfolios. Discipline: CRYPTO. Governing mathematical model / formula: Sharpe Ratio = (Expected Return - Risk-Free Rate) / Portfolio Volatility (σ).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of calculated_sharpe_ratio (Portfolio Sharpe Ratio), daily_var_95_usd (1-Day 95% Value at Risk (VaR)), monthly_var_95_usd (1-Month 95% Value at Risk), risk_adjusted_grade (Risk-Adjusted Performance Grade) using portfolio_value_usd (Total Portfolio Capital ($ USD)), annual_expected_return_pct (Annual Expected Portfolio Return (%) in %), annual_volatility_sigma_pct (Annualized Volatility (σ %) in %), risk_free_rate_pct (Risk-Free Treasury Benchmark (%) in %). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Crypto Portfolio Sharpe Ratio & Value at Risk (VaR 95%) Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "crypto-portfolio-sharpe-ratio"

    • category (string): "crypto"

    • name (string): "Crypto Portfolio Sharpe Ratio & Value at Risk (VaR 95%) Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.calculated_sharpe_ratio (Portfolio Sharpe Ratio): Formatted display string (e.g. '0.68')

      • metrics.daily_var_95_usd (1-Day 95% Value at Risk (VaR)): Formatted display string (e.g. '$5,660.00 (5.66%)')

      • metrics.monthly_var_95_usd (1-Month 95% Value at Risk): Formatted display string (e.g. '$17,800.00 (17.8%)')

      • metrics.risk_adjusted_grade (Risk-Adjusted Performance Grade): Formatted display string (e.g. 'Moderate Alpha (High Volatility)')

    • execution_time_ms (number): Latency in milliseconds.

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

Input Schema

NameRequiredDescriptionDefault
risk_free_rate_pctNoRisk-Free Treasury Benchmark (%) (%). Current 3-month U.S. Treasury Bill yield. Default: 4.5. Min: 0. Max: 10.
portfolio_value_usdNoTotal Portfolio Capital ($ USD). Current total net asset value. Default: 100000. Min: 1000. Max: 100000000.
annual_expected_return_pctNoAnnual Expected Portfolio Return (%) (%). Historical or projected 12-month return. Default: 42. Min: -50. Max: 300.
annual_volatility_sigma_pctNoAnnualized Volatility (σ %) (%). Standard deviation of returns (BTC ~50%, ETH ~65%). Default: 55. Min: 10. Max: 150.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the entire burden and does so: it declares the tool read-only, idempotent, stateless, and side-effect free, explains validation against physical/domain bounds, and states that out-of-bounds inputs yield a safe diagnostic error rather than an exception. That is exactly the failure-mode and safety information a caller needs to invoke without hesitation.

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 sectioned layout (usage, disambiguation, behavior, returns) is front-loaded and scannable, and the returns block is genuinely necessary since no output schema exists. It loses a point for repetition: the tool name, formula, and full labels for each parameter are restated in multiple sections.

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?

No output schema and no annotations exist, yet the description documents the full response shape (status, calculator, formula, echoed inputs, metrics with example display strings) and the error behavior. For a stateless four-parameter calculator that is more than enough to call it correctly and interpret results.

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

Parameters4/5

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

Schema coverage is 100% and each parameter already carries units, defaults, and min/max, so the schema does most of the work. The description adds marginal value by tying the parameters into the Sharpe formula (expected return minus risk-free rate over volatility) and by naming them alongside the outputs they drive, but it largely restates what the schema documents.

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-and-resource pair (calculate Sharpe Ratio, Sortino, and 95% VaR for crypto portfolios) plus the governing formula, and the inputs/outputs listed make the computation concrete. An agent can distinguish it from omni_crypto_fifo_lifo_tax or omni_algorithmic_lending_apy on the strength of the description alone.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE with the exact output fields produced, an explicit WHEN NOT TO USE (no qualitative evaluation, numeric inputs only), and named alternatives for adjacent cases: omni_universal_query for generic dispatch, omni_batch_calculate for chained jobs, omni_describe_solver for schema inspection. This is a full routing decision table.

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

Deploy Server

Other Tools