Skip to main content
Glama

risk_report

Read-onlyIdempotent

Computes drawdown-first risk metrics including max drawdown, Ulcer, CDaR, and Sharpe/Sortino/Calmar with bootstrap confidence intervals. Also provides annualized time-weighted return for portfolio risk assessment.

Instructions

Drawdown-first risk panel for the held portfolio: max drawdown (depth/dates/recovery + CI), Ulcer, CDaR, and Sharpe/Sortino/Calmar with bootstrap confidence intervals, plus the annualized time-weighted return (it rides on the same daily history). Offline, read-only. Use to answer 'how risky / how deep are the drawdowns' — and for the time-weighted return portfolio_summary can't compute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
asofYes
cdarNomean of the worst-5% drawdowns (positive magnitude)
noteNoRead-only: figures are derived from your transaction log and the on-disk price cache. Uncached prices are fetched online on demand — a one-time core warm on the first cold call, plus any new ticker you ask about (set ASSET_MCP_OFFLINE=1 to keep it strictly offline); a value still unavailable shows null (n/a), never a guess. This is a view, not financial advice.
calmarNonull when there's no drawdown (undefined)
n_daysYes
sharpeYes
sortinoNonull with no downside days (undefined)
is_noisyYesTrue when under ~2 trading years — bands are wide
provenanceYes
ulcer_indexNoRMS drawdown (positive magnitude)
max_drawdownYes
dollar_drawdownYes
true_twr_annualizedNoannualized time-weighted return (252-day basis) from the same daily series as this panel — the one tool that carries it; null only when the window is too short to annualize (< 20 return-days)
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint true. Description adds 'Offline, read-only' and details the computed metrics with bootstrap confidence intervals, providing useful behavioral context beyond annotations.

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?

Description is well-structured and front-loaded with the main purpose. Every sentence adds value, though slightly verbose – could be trimmed without losing clarity.

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?

Given zero parameters and presence of output schema (not shown), description fully explains the tool's purpose and the metrics it produces. It is complete for an AI agent to understand when and what it does.

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?

Input schema has zero parameters with 100% coverage, so description need not add parameter info. Baseline score of 4 applies.

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?

Description clearly states the tool provides a drawdown-first risk panel with specific metrics (max drawdown, Ulcer, CDaR, Sharpe, Sortino, Calmar with confidence intervals, and time-weighted return). It distinguishes from sibling portfolio_summary by noting that portfolio_summary cannot compute time-weighted return.

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?

Explicitly states when to use: to answer 'how risky / how deep are the drawdowns' and for time-weighted return that portfolio_summary cannot compute. Does not explicitly state when not to use, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/disin7c9/asset-management'

If you have feedback or need assistance with the MCP directory API, please join our Discord server