Skip to main content
Glama

Profit Margin Calculator API - margin, markup, price from cost

profit_margin_calculator
Read-onlyIdempotent

From cost and price get margin %, markup % and profit; or from cost and wanted margin/markup get the selling price; optional VAT on top. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/profit-margin-calculator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cost": 60,
      "mode": "cp",
      "price": 100
    },
    "name": "profit_margin_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
vatNoVAT % on top (optional)
costNoCost
modeNocp cost+price, cm cost+margin %, ck cost+markup %cp
priceNoSelling price (mode=cp)
percentNoMargin or markup percent (mode=cm/ck)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, yet the description still adds real operational context: server-side execution, immediate file deletion with nothing stored, a 25 calls/day free quota per IP, and a $0.001 paid path via x402. The file-deletion note is slightly incongruous for a tool with no file parameters, which keeps it from a 5.

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

Conciseness4/5

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

The core capability is front-loaded in one dense sentence, followed by a short privacy/pricing sentence. No filler, though the access-and-pricing tail is somewhat long relative to the computational content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five optional parameters, no output schema and full annotation coverage, the description supplies what an agent needs: the input-to-output mapping for each mode plus rate-limit and payment details. Nothing critical is missing, though the mode-to-parameter binding could be stated explicitly rather than inferred.

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 description coverage is 100%, so mode enum values, cost, price, percent and vat are already documented in the schema. The description only reinforces that VAT is applied 'on top' and that percent means margin or markup depending on mode, which is a marginal addition over structured data.

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 computation and its outputs: margin %, markup %, profit from cost/price, or selling price from a target margin/markup, with optional VAT. That is concrete enough for an agent to distinguish it from generic arithmetic tools such as percentage_calculator without opening the schema.

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

Usage Guidelines3/5

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

The two operating modes are described and their inputs implied, which gives usable context for calling the tool. However, it never states when to prefer this over siblings like percentage_calculator or eu_vat_calculator, and no exclusions are given.

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.

Resources