Skip to main content
Glama
vosesoftware

ModelRisk MCP

Official
by vosesoftware

create_cdf_chart

Generate a cumulative probability distribution chart (CDF) for a simulation output, showing the chance the output is below a given value. Creates a new sheet with binned data and an Excel line chart.

Instructions

ModelRisk: Render the ascending cumulative-probability curve (CDF) of one output's simulation result distribution as a new sheet in the workbook. The sheet has a binned data table plus a native Excel line chart of cumulative probability (0-100%) against the output value — the 'what's the chance the output is below X' view. Requires a completed simulation (reads samples from the active .vmrs). Idempotent — a sheet with the target name is replaced.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_nameNoTarget sheet name. Default: `CDF_<output_name>` (truncated to Excel's 31-char limit).
output_nameYesVoseOutput name to chart.
workbook_nameNoWorkbook name. Omit for the active workbook.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses creation of a new sheet with binned data table and Excel line chart, replacement of existing sheets, and prerequisite of completed simulation. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three sentences, each essential: purpose, chart type/behavior, prerequisites/idempotency. No redundant or trivial content.

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 moderate complexity and full schema coverage, the description covers all key aspects: output (sheet with data+chart), prerequisite, idempotency, and default naming. Output schema exists, so return values need not be detailed.

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%. Description adds value by explaining default sheet name pattern and Excel's 31-character truncation, going beyond the schema's bare definitions.

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?

Clearly states it renders a cumulative probability curve (CDF) of a simulation output as a new sheet, distinguishing it from sibling histogram or tornado chart tools.

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?

Specifies that a completed simulation is required and that the tool is idempotent. Implicitly differentiates from histogram (PDF) by describing the CDF perspective; lacks explicit when-not or alternative comparisons.

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