Skip to main content
Glama

Business Calculator: GST, Margin & Everyday Formulas

Pricing, Margin & Discount Calculators — Saifs AI

pricing_profit_calculators
Read-only

Calculate prices, profit and percentages exactly: what is 18% of a price, % change, percentage points, reverse %; price from target margin, margin vs markup; single / chain (10% + 5%) / trade + cash discounts, MRP back-calculation; profit or loss % on cost and on sale; slab / volume pricing, sales commission slabs, incentive payout; break-even units and revenue, contribution margin, target-profit units, margin of safety; split an amount by a ratio, rule of three. Returns a standard-library Python script with only these calculators (percentage_calculator, margin_markup_calculator, discount_calculator, profit_loss_calculator, tier_pricing_commission_calculator, break_even_calculator, ratio_proportion_calculator) to run in your code sandbox; each answer gives result, formula, inputs used, rounding, rule version and effective date. Inputs: tools (narrow to some of these calculators), calls ([{tool, operation, inputs, rounding?, as_of?}] baked into the script; a calculator from another area named in calls is added), calls_path (JSON file of calls in your sandbox). Calculation never runs on this server or any API. Not for EMI / interest / NPV / IRR (refused), nor win-probability pricing (Saifs MCP 59); GST (use gst_tds_invoice_calculators). Operation and input names: business_calculator_list_formulas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pricing_profit_calculators"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsNoCalculations to bake into the script (their calculators are included).
toolsNoNarrow the script to some of this area's calculators (default: all of them).
calls_pathNoJSON file of calls already in your sandbox.
full_catalogNoKeep descriptions and worked examples inside the script (larger).

Output Schema

NameRequiredDescriptionDefault
areaNo
notesNo
scriptYes
languageNo
requiresNo
calls_pathNo
operationsNo
call_formatNo
instructionsYes
writes_filesNo
calls_baked_inNo
engine_versionYes
included_toolsYes
server_computesNo
network_access_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/closed-world/no-destruction, but the description adds the decisive behavioral fact that no calculation runs on the server or any API — the payload is a sandbox script — which changes how an agent must handle the response. It further discloses output shape (result, formula, inputs used, rounding, rule version, effective date) and the side effect that a calculator from another area named in calls is silently added to the script.

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

Conciseness3/5

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

Front-loading is good, but the middle is a single semicolon-chained catalog of every calculation type that is hard to scan and partly redundant with the pointer to business_calculator_list_formulas for operation names. The density costs readability even though most clauses carry real information.

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 multi-calculator, script-generating tool with a full output schema and complete parameter documentation, nothing an agent needs is missing: scope, refusals, alternatives, input channels (calls, calls_path, tools, full_catalog), and return contract are all present.

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 baseline is 3; the description earns above that by explaining the semantics of calls ('baked into the script'), tools (narrowing), and calls_path (a JSON file of calls in your sandbox), plus the cross-area inclusion rule not expressible in the schema. It stops short of covering the per-call fields like rounding modes or as_of, leaving those to the schema.

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 opening clause names concrete verbs and resources (calculate prices, profit, percentages, margins, discounts, break-even, ratios) and enumerates exactly which seven calculators ship in the returned script, so the agent can distinguish this from gst_tds_invoice_calculators or finance_mis_calculators without opening the schema. It also states the unusual output form (a standard-library Python script) up front rather than burying it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit exclusions are given ('Not for EMI / interest / NPV / IRR (refused), nor win-probability pricing (Saifs MCP 59); GST (use gst_tds_invoice_calculators)'), which is exactly the when-not-to-use routing an agent needs. It also points to business_calculator_list_formulas for operation and input names, resolving the discoverability question the caller would otherwise have.

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.