Skip to main content
Glama
tresor4k

macalc

calculate_churn_rate

Compute customer or revenue churn rate for a specified period. Enter starting customers and churned count to receive churn percentage, retention rate, and annualized churn. Suitable for SaaS retention analysis.

Instructions

Compute customer or revenue churn rate over a period. Use for SaaS retention analysis. Inputs: starting customers, churned, period length. Returns churn %, retention %, and annualized rate. See list_bundles for related 'finance-universal' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_customersYesCustomers at period start
lost_customersYesCustomers lost
period_monthsNoPeriod in months

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.
Behavior2/5

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

No annotations provided, so description carries full burden. It briefly mentions outputs (churn %, retention %, annualized rate) but lacks details on permissions, rate limits, or side effects. Minimal behavioral disclosure.

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?

Extremely concise: two sentences cover purpose, inputs, outputs, and related tools. Front-loaded with purpose, no filler.

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?

Covers purpose, inputs, outputs, and points to related calculators. Output schema exists, so return values are documented elsewhere. Complete for a simple calculator tool.

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%, baseline score. Description repeats parameter names but adds no semantic detail beyond schema descriptions (e.g., 'starting customers' vs 'Customers at period start'). No additional clarity.

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?

Clearly states it computes churn rate for SaaS retention, with specific verb 'compute' and resource 'churn rate'. Distinguishes from other calculators by pointing to 'finance-universal' bundle, aiding differentiation among many siblings.

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 usage context ('SaaS retention analysis') and lists expected inputs. Does not explicitly state when not to use or compare to specific siblings, but points to bundle for related tools, offering some guidance.

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