Skip to main content
Glama

Estimate startup costs

estimate_startup_costs
Read-onlyIdempotent

Adds up one-time startup costs and monthly costs and works out cash left and months of runway (cash left divided by monthly costs, rounded down to 0.1, assuming no sales). Same formula as https://profitdrawer.com/tools/startup-cost-calculator.html. Optional preset with example amounts: Cleaning, Lawn care, Vending machine, Food truck, Any business; cost lists you pass replace the preset lines. Preset amounts are rough examples, not quotes.

Input Schema

NameRequiredDescriptionDefault
presetNoExample cost lines from the website calculator.
monthly_costsNoMonthly costs [{label, amount}] in USD. Replaces the preset monthly lines.
starting_cashNoStarting cash in USD. Default 0.
one_time_costsNoOne-time costs [{label, amount}] in USD. Replaces the preset one-time lines.

Output Schema

NameRequiredDescriptionDefault
urlYes
notesNo
presetNo
runwayYes
displayNo
short_byNo
cash_leftYes
citationsYes
monthly_costsNo
monthly_totalYes
runway_monthsYes
sample_noticeNo
starting_cashNo
one_time_costsNo
one_time_totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the exact formula, the rounding behavior, the key assumption of no sales, and the replacement semantics between presets and supplied cost lists. These are meaningful behavioral details for interpreting the calculation correctly.

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 front-loaded with the core calculation and rounding rule, then covers the preset behavior. It is appropriately sized, though the website-reference sentence and preset enumeration add some density.

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?

With rich annotations, full schema descriptions, an output schema, and a clear formula explanation, the description gives an agent everything needed to call the tool and interpret its calculation assumptions.

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%, so the baseline is 3. The description adds useful inter-parameter semantics: cost lists replace preset lines, and presets are rough examples, not quotes. It could say more about starting_cash or the distinction between cost arrays, but the schema already covers those.

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 names a specific calculation: summing one-time and monthly startup costs, computing cash left and runway, with rounding details. It clearly separates this startup-cost calculation from sibling tools like loan payoff or tax set-aside calculators by domain and output.

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 explains how presets interact with passed cost lists and that preset amounts are examples, which guides parameter use. However, it does not explicitly state when to use this tool versus the sibling calculators or when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources