Skip to main content
Glama

BRAINIAC Ecommerce Seller Profitability

Per-unit contribution margin and break-even

ecommerce-profitability_unit-economics
Read-onlyIdempotent

Compute landed cost, total cost per unit, contribution margin, ROI, break-even price and break-even ACoS from caller-supplied product costs and marketplace fees or fee rates. Price $0.03 USDC. POST /api/v1/ecommerce-profitability/unit-economics. An unpaid call returns the x402 payment terms and does not run.

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": {
      "currency": "<currency>",
      "pricePerUnit": "<pricePerUnit>",
      "costs": "<costs>",
      "returnRate": "<returnRate>",
      "returnLossPerUnit": "<returnLossPerUnit>"
    },
    "name": "ecommerce-profitability_unit-economics"
  }
}

Input Schema

NameRequiredDescriptionDefault
costsYescosts, object. Required.
currencyYescurrency, string, length 3 to 3. Required.
returnRateYesreturnRate, number, from 0 to 1. Required.
pricePerUnitYespricePerUnit, integer, from any to 9007199254740991. Required.
salesTaxIncludedNosalesTaxIncluded, boolean. Required.
returnLossPerUnitYesproduct, integer, from 0 to 9007199254740991. Required.
marketplaceFeeRateNomarketplaceFeeRate, number, from 0 to any. Optional.

Output Schema

NameRequiredDescriptionDefault
roiNoroi. Number.
sourcesNosources. Array.
currencyNocurrency. String.
marginPctNomarginPct. Number.
landedCostNolandedCost. Number.
limitationsNolimitations. Array.
breakEvenAcosNobreakEvenAcos. Number.
breakEvenPriceNobreakEvenPrice. Number.
marketplaceFeesNomarketplaceFees. Number.
returnsAllowanceNoreturnsAllowance. Number.
salesTaxIncludedNosalesTaxIncluded. Boolean.
totalCostPerUnitNototalCostPerUnit. Number.
contributionMarginNocontributionMargin. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond them: the tool is metered at $0.03 USDC, the transport is POST /api/v1/ecommerce-profitability/unit-economics, and an unpaid invocation returns x402 payment terms instead of executing. That payment-failure semantics is exactly the kind of context annotations cannot express.

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?

Three sentences, front-loaded with the computation being performed and the output set, followed by pricing and endpoint, then the payment-failure condition. No filler or restatement of the name.

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 an output schema present, return values need no prose, and the 7 parameters (5 required, nested `costs` object) are fully documented in schema. The definition covers cost, endpoint, and payment semantics adequately; the remaining gap is the absence of routing guidance among closely related profitability siblings.

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 the baseline is 3. The phrase "marketplace fees or fee rates" hints that `marketplaceFees` and `marketplaceFeeRate` are alternatives, which is a small value-add. However, the description does not clarify the unit convention for the integer cost/price fields (minor currency units vs. whole units) or what the 3-character `currency` code must be, leaving real ambiguity for a monetary calculation.

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?

States a precise verb ("Compute") and enumerates the exact outputs: landed cost, total cost per unit, contribution margin, ROI, break-even price and break-even ACoS, plus the input basis (product costs and marketplace fees/rates). An agent knows exactly what it gets back. It stops short of naming how it differs from the overlapping sibling `ecommerce-profitability_landed-cost-import`, which also deals with landed cost.

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?

The description contains no when-to-use or when-not-to-use guidance relative to the eight sibling tools; the only conditional statement is about payment (unpaid calls return x402 terms and do not run). An agent must infer from the output list alone whether to call this or `landed-cost-import` / `bundle-pricing`.

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