Skip to main content
Glama
vosesoftware

ModelRisk MCP

Official
by vosesoftware

fit_distribution_to_data

Fit a distribution family to a data range in Excel, write the result to a target cell, and optionally include parameter uncertainty for Monte Carlo risk modeling.

Instructions

ModelRisk: Fit a distribution family to a data range and write the result. 'family' is e.g. 'Normal', 'Lognormal', 'Beta', 'Gamma', 'Weibull' — the tool maps it to the catalogue function (VoseFit). Set uncertainty=True (the default) to include parameter uncertainty in the fitted distribution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheetYes
familyYesDistribution family, e.g. 'Normal'.
dry_runNo
workbookYes
as_objectNoWrite Vose<Family>FitObject(...) instead of the sampling Vose<Family>Fit(...). The OBJECT form is what compute_distribution / VoseMean / VosePercentile need to answer analytic questions about the fit; the sampling form is what a simulated model input needs. Default False (sampling).
data_rangeYes
target_cellYes
uncertaintyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cellYes
formulaYes
writtenYes
previous_formulaNo
Behavior4/5

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

Despite no annotations, the description discloses key behavioral traits: the mapping of 'family' to Vose<Family>Fit, the inclusion of parameter uncertainty via 'uncertainty', and the distinction between sampling and object forms via 'as_object'. However, it does not mention side effects like overwriting cells or error handling, leaving some gaps.

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 three sentences long and front-loads the main purpose. It efficiently covers the key points but could be slightly more concise by reducing redundancy in the first sentence.

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?

Given the complexity (8 parameters, 5 required, extensive sibling list), the description provides core functionality but lacks details on error conditions, data range validation, and behavior of 'dry_run'. The presence of an output schema reduces the need to explain return values, but the description is still not fully complete for practical use.

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

Parameters3/5

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

With only 25% schema description coverage, the description compensates for 'family' and 'uncertainty' semantics, but other parameters like 'sheet', 'target_cell', 'data_range', and 'dry_run' are not explained beyond their names and types. The description adds value for the core parameters but is insufficient for full guidance.

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 the tool fits a distribution family to a data range and writes the result, with explicit examples of families like 'Normal', 'Lognormal', etc. It distinguishes itself from sibling tools like 'fit_and_rank_distributions' and 'fit_tail' by focusing on a single family fit.

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?

The description lacks explicit guidance on when to use this tool vs alternatives. It explains the 'family' and 'uncertainty' parameters but does not clarify when to choose this over sibling tools like 'fit_and_rank_distributions' or 'fit_tail'. No prerequisites or exclusions are mentioned.

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