出口单 chukoudan

亚马逊费用

amazon-fees

Read-onlyIdempotent

亚马逊费用（Amazon fees and profit）：填入售价、成本和亚马逊的各项费用，算出每件和整批的净利润、利润率和保本价。 Enter the price, your cost and your own Amazon fees to get the net profit per unit and per batch, the margin and the break-even price. 输入为精确的十进制字符串 / Inputs are exact decimal strings. 用户没有给的数字和日期不要自己编：必填的先问用户，选填的不填。 / Never make up a figure or a date the user did not give: ask for a required one, leave an optional one out. 回复时引用回答里的 provenance.source_line / Quote provenance.source_line in your reply. 结果仅供计算参考，不是税务、法律或投资意见；回答时请带上返回的说明和来源行。 / The result is for calculation and reference only, not tax, legal or investment advice; when you answer, pass on the returned notice and source line.

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": "6",
      "price": "25",
      "adsRate": "10",
      "currency": "USD",
      "quantity": "1000",
      "otherCost": "0.5",
      "returnRate": "5",
      "storageFee": "0.10",
      "inboundCost": "1",
      "referralRate": "10",
      "targetMargin": "20",
      "fulfilmentFee": "4",
      "storageMonths": "2"
    },
    "name": "amazon-fees"
  }
}

Input Schema

Name	Required	Description
`cost`	Yes	每件采购成本 / Purchase cost per unit
`price`	Yes	每件售价 / Selling price per unit
`adsRate`	No	广告费占售价（%） / Advertising as a share of the price (%)
`currency`	No	币种 / Currency
`quantity`	Yes	订单数量（件） / Order quantity (units)
`otherCost`	No	每件其他成本 / Other cost per unit
`returnRate`	No	退货率（%） / Return rate (%)
`storageFee`	No	每件每月仓储费 / Storage fee per unit per month
`inboundCost`	No	每件头程运费 / Inbound shipping per unit
`referralRate`	Yes	佣金比例（%） / Referral fee rate (%)
`targetMargin`	No	目标利润率（%，按售价） / Target margin (% of the price)
`fulfilmentFee`	Yes	每件配送费 / Fulfilment fee per unit
`storageMonths`	No	存放月数（月） / Months stored (months)

Output Schema

Name	Required	Description	Default
`tool`	Yes
`links`	Yes
`steps`	Yes
`outputs`	Yes
`warnings`	Yes
`normalized`	No
`provenance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / description

Previous value: -"数字最好写成字符串（十进制，如 \"12.5\"），JSON 数字也行；千位逗号只认 1,234,567 这种写法，小数点用英文句点，不要带货币符号或单位。币种可写 USD、usd 或 美元，单位可写 cm 或 厘米，日期可写 2026-05-01、2026/05/01 或 20260501。读不准的一律拒绝并说明原因，绝不猜；回答里的 normalized 列出实际采用的值。 / Figures are best sent as decimal strings such as \"12.5\"; a JSON number is accepted too. A thousands comma only as 1,234,567; the decimal point is a dot; no currency symbols or units. A currency may be USD, usd or 美元, a unit cm or 厘米, a date 2026-05-01, 2026/05/01 or 20260501. Anything that cannot be read in exactly one way is refused with a reason, never guessed; `normalized` in the answer lists what was used."New value: +"数字最好写成字符串（十进制，如 \"12.5\"），JSON 数字也行；千位逗号只认 1,234,567 这种写法，小数点用英文句点，不要带货币符号或单位。币种可写 USD、usd 或 美元，单位可写 cm 或 厘米，日期可写 2026-05-01、2026/05/01 或 20260501。读不准的一律拒绝并说明原因，绝不猜；回答里的 normalized 列出实际采用的值。 / Figures should be sent as decimal strings such as \"12.5\"; a JSON number is accepted too. A thousands comma only as 1,234,567; the decimal point is a dot; no currency symbols or units. A currency may be USD, usd or 美元, a unit cm or 厘米, a date 2026-05-01, 2026/05/01 or 20260501. Anything that cannot be read in exactly one way is refused with a reason, never guessed; `normalized` in the answer lists what was used."

AddedNov 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive calculation. The description adds valuable behavioral context beyond the annotations: exact decimal-string handling, never inventing missing figures, quoting provenance.source_line, and passing on the disclaimer notice.

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?

The purpose is front-loaded and the content is organized, but the bilingual duplication and repeated cautionary statements make the description longer than necessary. Every clause is relevant, but the same guidance is effectively stated twice.

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?

Given 13 parameters, full schema coverage, an output schema, and read-only annotations, the description covers the key usage constraints: input formatting, missing-value handling, provenance quoting, and the disclaimer. It is complete enough to invoke the tool correctly, though it could be stronger with explicit sibling routing guidance.

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 description coverage is 100%, so the schema already documents all 13 parameters. The description still adds useful semantics by clarifying exact decimal strings, asking for required values instead of guessing, leaving optional values out, and explaining that normalized lists the values actually used.

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 description states a specific verb and resource: calculating Amazon fees, net profit per unit and per batch, margin, and break-even price. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as lc-fees or baojia.

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 description explains what inputs to provide and what results are returned, which implies when the tool is useful. However, it gives no explicit when-to-use guidance, exclusions, or alternatives among the sibling fee and quotation tools.

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

All 出口单 chukoudan tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?