Skip to main content
Glama
tresor4k

macalc

calculate_break_even

Calculate break-even point in units and revenue for business planning and pricing decisions using fixed costs, price per unit, and variable cost per unit.

Instructions

Compute break-even point in units and revenue. Use for business plans and pricing decisions. Inputs: fixed costs, price/unit, variable cost/unit. Returns break-even units and revenue. See list_bundles for related 'finance-universal' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fixed_costsYesTotal fixed costs
price_per_unitYesSelling price per unit
variable_cost_per_unitYesVariable cost per unit

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

No annotations provided, so description carries full burden. It states returns break-even units and revenue, but does not disclose behavior for edge cases (e.g., invalid inputs, negative results) or assumptions (e.g., linearity). Adequate but not thorough.

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?

Two sentences with no wasted words. Purpose, usage, inputs, outputs, and cross-reference are all front-loaded and logically ordered. Very efficient.

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?

For a simple calculator with full schema coverage and an output schema present, the description is complete enough. It tells the user what the tool does, what inputs are needed, what outputs result, and where to find similar tools.

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?

Schema coverage is 100% with descriptions for each parameter. Description restates parameter names but adds no additional meaning beyond the schema. Baseline 3 applies.

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?

Description clearly states the tool computes break-even point in units and revenue, specifying use for business plans/pricing decisions. Verb 'Compute' and resource 'break-even point' are specific. Distinguishes from siblings by referencing a bundle of related calculators.

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?

Provides clear context: 'Use for business plans and pricing decisions.' Directs user to list_bundles for related calculators, implying when to use alternatives. Lacks explicit when-not-to-use but sufficient for this tool.

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/tresor4k/macalc-mcp'

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