Skip to main content
Glama
vosesoftware

ModelRisk MCP

Official
by vosesoftware

fit_tail

Fit an extreme-value tail (GPD, GEV, etc.) to data and compute tail risk (mean, P95, P99, P99.5, P99.9) analytically without simulation. Writes a fit object for further analysis.

Instructions

ModelRisk: Fit an extreme-value / Generalised-Pareto tail to data and read its risk. family is 'GPD' (peaks-over-threshold, the standard tail model), 'GEV' (block maxima), 'ExtValueMax', or 'ExtValueMin'. For GPD peaks-over-threshold, pass the range of exceedances above your threshold as data_range. Writes a VoseFitObject (dry_run previews) and returns the fitted tail's mean and high percentiles (P95 / P99 / P99.5 / P99.9) computed analytically — the tail risk without a simulation. Feed the written object cell to compute_distribution / get_tail_risk for more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheetYes
familyNo'GPD' (default), 'GEV', 'ExtValueMax', or 'ExtValueMin'.GPD
dry_runNo
workbookYes
data_rangeYesA1-style range of the tail data.
target_cellYes
uncertaintyNoFit with parameter uncertainty. Default True.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
meanYes
familyYesTail family fitted, e.g. 'GPD' or 'GEV'.
writtenYes
data_rangeYes
percentilesYesFitted-tail percentiles, e.g. {'P95': ..., 'P99': ..., 'P99.5': ...}.
object_formulaYesThe Vose<Family>FitObject formula written (or previewed).
Behavior3/5

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

Describes that it writes a Vose<Family>FitObject (with dry-run preview) and returns mean/high percentiles analytically. No annotations exist, so description carries full burden; lacks details on side effects, permissions, or limitations.

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 sentences pack purpose, usage, parameters, and output. Front-loaded with action verb. Could be slightly more concise but each sentence adds value.

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?

Covers purpose, parameters, behavior, and output (mean, high percentiles). Output schema exists but description explains return values. Adequate for an agent to understand and invoke correctly.

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?

Adds meaning beyond schema by explaining 'data_range' as exceedances above threshold for GPD, and lists family options. Schema coverage is only 43%, so description compensates with context like 'dry_run previews' and 'uncertainty'.

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?

The description clearly states it fits extreme-value tails (GPD, GEV, etc.) to data and returns risk metrics. It distinguishes itself from sibling tools like fit_distribution_to_data and get_tail_risk by specifying the output and follow-up actions.

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?

Indicates when to use: for fitting tails and obtaining risk percentiles. Mentions alternative tools (compute_distribution, get_tail_risk) for further analysis. However, does not explicitly state when not to use or compare to other fitting tools.

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/vosesoftware/modelrisk-mcp'

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