Skip to main content
Glama

Moltline Business Suite

by com.moltlinestudio

Unit Economics

unit_economics
Read-onlyIdempotent

Calculate unit economics: margin, break-even, LTV:CAC, and a plain reading. FREE.

Typical input {"price": 49, "unit_cost": 12, "fixed_costs_monthly": 8000} returns {"unit_margin": 37.0, "margin_pct": 75.5, "markup_pct": 308.3, "breakeven_units_per_month": 216.2, "reading": ["..."]}. LTV fields appear when cac is provided.

Use when price, variable cost, and fixed costs are known and margin or break-even is the question. Not for cash position over time (cash_runway) and not for solving backward from a target margin (target_price). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "price must be > 0"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cacNoCustomer acquisition cost; a value greater than 0 enables LTV and LTV:CAC. Default 0 (skipped).
priceYesSelling price per unit; must be greater than 0, e.g. 49.0.
unit_costYesVariable cost per unit, in the same currency as price, e.g. 12.0.
units_per_monthNoExpected sales volume per month; a value greater than 0 enables the monthly profit projection. Default 0 (skipped).
fixed_costs_monthlyNoFixed monthly costs; a value greater than 0 enables the break-even calculation. Default 0 (skipped).
purchases_per_customerNoAverage lifetime purchases per customer used for LTV. Default 1.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description reinforces these and adds valuable error behavior: 'on invalid, missing, or malformed input this tool never raises a protocol error — it returns an error object with a fix message.' No contradictions, but additional details like rate limits or auth are absent.

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?

Well-structured single paragraph: purpose first, then example, usage guidelines, error behavior. No unnecessary sentences. The word 'FREE' is minor and doesn't detract. Efficient and front-loaded.

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 6 parameters, high schema coverage, existing output schema, and clear sibling differentiation, the description covers purpose, input/output examples, conditional behaviors, error handling, and retry safety. An agent can confidently use this tool.

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 adds a concrete example (price=49, unit_cost=12, fixed_costs_monthly=8000) and explains conditional behavior: 'LTV fields appear when cac is provided.' This enhances understanding beyond schema alone.

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 clearly states 'Calculate unit economics: margin, break-even, LTV:CAC, and a plain reading.' It provides a specific verb and resources, includes an example input/output, and distinguishes from siblings like cash_runway and target_price.

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 guidance: 'Use when price, variable cost, and fixed costs are known and margin or break-even is the question. Not for cash position over time (cash_runway) and not for solving backward from a target margin (target_price).' Also explains error handling and safe retry behavior.

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

All Moltline Business Suite toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation3/5

The financial calculation tools (cash_runway, loan_payment, target_price, unit_economics) are clearly distinct in their inputs and outputs. However, within the product listing tools (list_products, get_free_skill, get_full_skill, get_full_product), the differentiation relies heavily on the 'FREE' vs 'PREMIUM' tags and the notion of 'free gateway skill' vs 'paid skills', which creates some ambiguity. An agent could easily pick get_free_skill when it actually needs get_full_skill.

Naming Consistency4/5

The tool set uses a mix of verb_noun (list_products, get_free_skill, get_full_product) and simple noun phrases (cash_runway, loan_payment, target_price, unit_economics). While the 'get_*' prefix creates a consistent pattern for product/skill access, the standalone financial calculation tools break this pattern. Nevertheless, the naming is still clear and predictable within each subgroup.

Tool Count5/5

With 8 tools, the set is well-scoped for a 'business' server that covers two clear domains: financial calculations (4 tools) and product/skill browsing (4 tools). Each tool covers a distinct operation without redundancy, and the count feels appropriate for the stated purpose.

Completeness3/5

The financial calculation tools cover common business math (runway, loan payments, margin/pricing, break-even), but lack coverage for revenue metrics (e.g., ARR, MRR), ROI, or depreciation. The product browsing tools provide a clear CRUD-like flow (list -> get), but there is no way to search or filter products, and the missing 'search_catalog' is referenced as existing on another server. This is a minor gap that may require agents to switch servers.

Resources