Skip to main content
Glama

BRAINIAC Ecommerce Seller Profitability

Allocate import costs to SKU landed cost

ecommerce-profitability_landed-cost-import
Read-onlyIdempotent

Allocate shipment freight and insurance by value, weight or volume, compute CIF or FOB customs value, duty and import VAT from caller rates, and return per-unit landed cost. Price $0.04 USDC. POST /api/v1/ecommerce-profitability/landed-cost-import. 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>",
      "lines": "<lines>",
      "freight": "<freight>",
      "insurance": "<insurance>",
      "allocation": "<allocation>",
      "dutyBasis": "<dutyBasis>",
      "importVatRate": "<importVatRate>",
      "vatRecoverable": "<vatRecoverable>"
    },
    "name": "ecommerce-profitability_landed-cost-import"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYeslines, array. Required.
freightYesunitCost, integer, from 0 to 9007199254740991. Required.
currencyYescurrency, string, length 3 to 3. Required.
dutyBasisYesdutyBasis, string, one of CIF, FOB. Required.
insuranceYesunitCost, integer, from 0 to 9007199254740991. Required.
allocationYesallocation, string, one of value, weight, volume. Required.
importVatRateYesdutyRate, number, from 0 to 1. Required.
vatRecoverableYesvatRecoverable, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
linesNolines. Array.
totalsNototals. Object.
sourcesNosources. Array.
currencyNocurrency. String.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds material context beyond that: a concrete price of $0.04 USDC, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms without executing — behavior an agent cannot get from annotations or schema.

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?

Two tight sentences front-load the computation and then the payment/transport facts, with no filler. Every clause carries information the agent needs before invoking.

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 8 required parameters, an output schema and rich annotations, the definition covers purpose, cost model and invocation cost. Minor gaps remain, such as how vatRecoverable changes the returned landed cost and what the x402 flow requires to complete payment, but nothing essential to selecting the tool is missing.

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 the baseline is 3, but the description goes further by explaining what the parameters mean together: allocation can be by value, weight or volume, dutyBasis selects CIF or FOB customs valuation, and duty and import VAT are derived from caller-supplied rates. This compensates for weak schema text such as freight and insurance both being labeled 'unitCost'.

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 specific verbs and resources: allocate freight and insurance, compute CIF/FOB customs value, duty and import VAT, and return per-unit landed cost. It is unambiguous and clearly distinct from the pricing, elasticity and settlement siblings, which operate on different objects.

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?

Usage context is implied by the computation described (you bring freight, insurance, duty and VAT rates and get landed cost), but there is no explicit when-to-use or when-not guidance and no named alternative such as unit-economics or bundle-pricing. The agent must infer fit from the domain wording alone.

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