出口单 chukoudan

信用证手续费

lc-fees

Read-onlyIdempotent

信用证手续费（Letter of credit fees）：同意信用证之前先算清：你要付多少银行费用，实收多少。 Before you accept a letter of credit: what the bank fees come to and what is left for you. 输入为精确的十进制字符串 / 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": {
      "days": "120",
      "fees": [
        {
          "name": "通知费",
          "minimum": "300",
          "rateUnit": "permille",
          "chargedPer": "once",
          "minimumCurrency": "cny"
        },
        {
          "name": "议付/交单费",
          "rate": "1.5",
          "minimum": "100",
          "rateUnit": "permille",
          "chargedPer": "once",
          "minimumCurrency": "lc"
        },
        {
          "name": "保兑费",
          "rate": "1",
          "minimum": "200",
          "rateUnit": "permille",
          "chargedPer": "quarter",
          "minimumCurrency": "lc"
        },
        {
          "name": "快递费",
          "minimum": "60",
          "rateUnit": "permille",
          "chargedPer": "once",
          "minimumCurrency": "lc"
        }
      ],
      "term": "usance",
      "amount": "100000",
      "cnyPer": "1",
      "cnyRate": "6.7249",
      "currency": "USD",
      "daysPerQuarter": "90"
    },
    "name": "lc-fees"
  }
}

Input Schema

Name	Required	Description
`days`	No	远期天数 / Usance days
`fees`	Yes	银行费用 / Bank fees
`term`	No	付款期限。可选值：sight = 即期；usance = 远期 / Payment term. options: sight = Sight; usance = Usance
`amount`	Yes	信用证金额 / L/C amount
`cnyPer`	No	汇率按几个单位报价。可选值：1 = 每 1 单位；100 = 每 100 单位 / Rate is quoted per. options: 1 = per 1 unit; 100 = per 100 units
`cnyRate`	No	人民币折算汇率 / Yuan conversion rate
`currency`	No	币种 / Currency
`daysPerQuarter`	No	每季按几天算 / Days counted to a quarter

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.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so safety is covered. The description adds real behavioral context beyond them: inputs must be exact decimal strings, missing figures must be asked for rather than invented, provenance.source_line must be quoted in the reply, and the returned notice/source line must be passed on.

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?

Purpose is front-loaded in the first sentence, which is good. However, every sentence is duplicated in Chinese and English, roughly doubling length without adding information for any single reader.

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

Completeness5/5

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

With an output schema present, annotations covering safety, and full parameter documentation, the description only needs to supply intent, input etiquette, provenance quoting and the disclaimer — and it does all of these. Nothing an agent needs to invoke or report on this tool is missing.

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%, with enums documented for rateUnit, chargedPer, minimumCurrency, term and cnyPer, so the schema carries the parameter burden. The description adds only general input discipline (decimal strings, ask for required fields, omit optional ones), which is baseline-level value rather than per-parameter semantics.

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?

It states a concrete computation: bank fees payable and net proceeds remaining, framed around a letter of credit. An agent can tell this is an L/C fee estimator rather than a generic FX or freight tool, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

The opening clause 'Before you accept a letter of credit' gives an explicit trigger condition for calling the tool. It does not exclude cases or route to alternatives such as fx-cost or amazon-fees, so the guidance is contextual rather than fully discriminating.

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?