Skip to main content
Glama

Caelara Labs E-Commerce Intelligence

currency_margin_calc

Margin, markup, breakeven and target price with FX rate, fees, shipping and tax

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": "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 observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full burden of disclosure. It implies read-only computation by listing derived values, but does not state whether the result is per-unit or per-order, in which currency the outputs are expressed, or how the four computed figures are combined in the response. Naming the computed outputs is the only real behavioral signal.

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

Conciseness3/5

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

Very short with no wasted words, but the brevity comes at the cost of structure: a single unpunctuated fragment with no verb, no sentence delineating inputs from outputs. It is under-specified rather than genuinely concise.

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 calculator with no annotations and no output schema, the description is thin but does name the four outputs, giving some sense of what comes back. It omits output units/currency, ordering, and error behavior (e.g. what happens with mismatched cost/price currencies), which an agent would need for correct interpretation.

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 including fee_pct, fx_rate, tax_pct and target_margin_pct is already documented in the schema. The description merely echoes parameter names ('FX rate, fees, shipping and tax') without adding semantics such as whether tax_pct is applied before or after fees. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose3/5

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

Names a specific set of computed quantities (margin, markup, breakeven, target price) and the cost factors that feed them, which is more informative than the tool name alone. However, it is a bare noun phrase with no verb, so the agent must infer that the tool *calculates and returns* these values rather than, say, fetching them from a store. It does implicitly differentiate from the parser/detector siblings by being the only financial calculation tool.

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 tool, no prerequisites (e.g. that cost and price must be in the same or convertible currencies), and no mention of an alternative for related tasks. The agent is left to infer usage entirely from the name.

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