Skip to main content
Glama
vosesoftware

ModelRisk MCP

Official
by vosesoftware

write_formula

Write Excel formulas or values into a single cell. Protects existing formulas with overwrite control and supports dry runs for safety.

Instructions

ModelRisk: Write an arbitrary formula or value into a single cell. Use this for wiring cells (e.g. =A1*B1, =SUM(...), =IF(...), or links to other sheets) that aren't covered by the Vose-specific tools. Safety: refuses to overwrite a cell containing an existing formula unless allow_overwrite=True — that protects user-written formulas AND prior Vose distributions. Empty cells write freely. Defaults to dry_run=True; pass dry_run=False to commit. Every commit appends to the audit log so restore_cell can roll back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cellYesA1 cell reference like 'C1'.
sheetYes
dry_runNo
formulaYesFormula or value to write. Excel-style; leading '=' is optional (we'll add it if missing for non-numeric content).
workbookYes
allow_overwriteNoPermit overwriting a non-empty cell. Required if the cell already has any content. Without this flag the tool refuses and returns the existing formula so Claude can decide what to do.

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?

With no annotations provided, the description fully discloses key behaviors: overwrite protection (refusal unless allow_overwrite=True), dry_run default, and audit logging. Missing details like permissions or rate limits, but still strong for a mutation tool.

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 slightly long but well-structured and focused, front-loading the core purpose and then adding essential behavioral details without redundancy.

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 the existence of an output schema (not shown) and the tool's complexity, the description covers writing behavior, safety, dry run, and audit logging, making it sufficiently complete for an agent to use 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?

Schema covers only 50% of parameters with descriptions, but the description adds meaningful context: explains that '=' is optional in formula, the purpose of allow_overwrite, and dry_run behavior. This compensates for missing schema descriptions on workbook and sheet.

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 writes a formula or value into a single cell, provides examples, and distinguishes itself from Vose-specific tools, making its unique purpose evident.

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?

The description indicates when to use this tool (for arbitrary formulas not covered by Vose tools) and explains safety defaults (dry_run, overwrite protection), but does not explicitly name sibling tools as alternatives.

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