Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_ecom_currency_margin_calc

Calculate e-commerce margin, markup, breakeven, and target price using cost, selling price, FX rate, fees, shipping, and tax to set profitable cross-currency pricing.

Instructions

[E-Commerce Intelligence] Margin, markup, breakeven and target price with FX rate, fees, shipping and tax Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://ecom.caelaralabs.com.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cost": "<cost>",
      "price": "<price>"
    },
    "name": "caelara_ecom_currency_margin_calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYesUnit cost
priceYesSelling price
fee_pctNoMarketplace/payment fee percent
fx_rateNoFX multiplier cost currency to price currency (default 1)
tax_pctNoTax percent included in price
fixed_feeNoFixed fee per order
cost_currencyNoCost currency code
shipping_costNoShipping cost in price currency
price_currencyNoPrice currency code
target_margin_pctNoDesired margin percent for suggested price

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose that the tool makes a network call to https://ecom.caelaralabs.com and reports latency (p50 11 ms, p95 15 ms). It does not say whether the operation is read-only/pure computation, whether auth or keys are required, how rounding is handled, or what happens with invalid currency codes. That is partial but real 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.

Conciseness4/5

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

Two compact sentences plus a URL, front-loaded with the capability statement. Nothing is padded, though the fragmentary opening sentence would read better as a complete clause and the benchmark/URL tail is arguably secondary detail.

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

Completeness3/5

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

For a 10-parameter calculation tool with no output schema and no annotations, the description names the outputs at a high level but does not describe the returned shape, units, or how target_margin_pct drives the suggested price. It is adequate to attempt a call, but leaves the agent guessing about the response.

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 every parameter is already documented in the input schema, and the description only echoes the categories (FX, fees, shipping, tax) without adding format, default, or interaction rules. Baseline 3 is appropriate; for example it does not clarify how fx_rate interacts with cost_currency/price_currency.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'Margin, markup, breakeven and target price with FX rate, fees, shipping and tax' names the concrete outputs and inputs of a pricing calculator, which is enough to distinguish it from sibling ecommerce tools like the GTIN validator or price-drop comparator. It lacks an explicit verb ('compute/calculate') and the sentence is telegraphic, but the resource and result set are unmistakable.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives, no prerequisites, and no exclusions. The only adjacent sentence is the endpoint URL and benchmark, which is infrastructure detail rather than usage guidance.

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

Deploy Server

Other Tools