Skip to main content
Glama

Business Calculator: GST, Margin & Everyday Formulas

Finance, Accounts & MIS Calculators — Saifs AI

finance_mis_calculators
Read-only

Calculate finance and MIS figures exactly: gross / operating / net margin, current and quick ratio, debt-to-equity, working capital, asset turnover, ROE / ROA; DSO, DPO, DIO, cash conversion cycle, receivable / payable ageing buckets; budget vs actual (favourable / adverse), variance table, cost allocation by driver; depreciation schedules (straight-line, WDV, Income-tax half-rate rule); growth %, CAGR on values, market share, contribution to growth, index numbers. Returns a standard-library Python script with only these calculators (ratio_analysis_calculator, working_capital_days_calculator, budget_variance_calculator, depreciation_calculator, growth_share_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 interest, NPV, IRR, discounting, loan schedules (refused); cash-timing forecasts (MCP 64). 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": "finance_mis_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?

Beyond the readOnlyHint/openWorldHint=false annotations, the description discloses the crucial non-obvious behavior: no calculation runs on this server or any API, the output is a runnable script, each answer carries result, formula, inputs used, rounding, rule version and effective date, and a calculator from another area named in calls gets pulled in. That execution-model detail is exactly what an agent cannot infer from the annotations.

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?

The long semicolon-delimited enumeration of metrics is front-loaded and useful for selection, but it is a dense wall of text with several overloaded sentences. Some of the formula listing could be deferred to business_calculator_list_formulas, which the description already references.

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 four optional parameters, an output schema, and read-only annotations, the description covers the execution model, the refusal boundary, the output contract, and the cross-area extension rule. An agent has everything needed to decide whether to call it and how to shape calls.

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, and the description earns extra by explaining that calls entries are 'baked into the script' rather than executed, that tools defaults to all calculators, and that calls_path reads a JSON file already in the sandbox. The cross-area inclusion rule for calls is genuine semantics not present in 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 description names a specific verb and a concrete set of resources (gross/operating/net margin, current/quick ratio, DSO/DPO/DIO, depreciation schedules, CAGR), and states the actual deliverable: a standard-library Python script built from five named calculators. It is clearly distinguishable from siblings such as gst_tds_invoice_calculators or hr_payroll_calculators by enumerating what falls inside this area.

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 (EMI / interest / NPV / IRR / discounting / loan schedules are refused; cash-timing forecasts belong to MCP 64), plus a routing pointer to business_calculator_list_formulas for operation and input names. It also explains the three input modes (tools to narrow, calls to bake in, calls_path for a sandbox file), so an agent knows which path to take.

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.