Skip to main content
Glama
Sign In

出口单 chukoudan

by com.chukoudan
OverviewDiscussionsAdmin

货运保险费

cargo-insurance
Read-onlyIdempotent

货运保险费（Cargo insurance premium）：算 CIF 保险费、CIF 价和投保金额，可填最低保费。 Premium, CIF price and insured amount, with an optional minimum premium. 输入为精确的十进制字符串 / 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": {
      "rate": "0.5",
      "price": "2",
      "markup": "110",
      "freight": "2000",
      "currency": "USD",
      "quantity": "10000",
      "rateUnit": "percent"
    },
    "name": "cargo-insurance"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYes保险费率 / Insurance rate
priceYesFOB 单价 / FOB unit price
markupNo投保加成（%） / Insured at (% of CIF)
freightNo运费及其他费用 / Freight and other charges
minimumNo最低保费 / Minimum premium
currencyNo币种 / Currency
quantityYes数量 / Quantity
rateUnitNo费率单位。可选值：percent = %（百分比）；permille = ‰（千分比） / Rate is in. options: percent = % (per cent); permille = ‰ (per mille)

Output Schema

NameRequiredDescriptionDefault
toolYes
linksYes
stepsYes
outputsYes
warningsYes
normalizedNo
provenanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed1 schema field changed
    • changedOutput schema / $defs / PlainValue / oneOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "amount": {
-        "type": "string"
-      },
-      "currency": {
-        "description": "An ISO 4217 code.",
-        "type": "string"
-      },
-      "kind": {
-        "const": "money"
-      }
-    },
-    "required": [
-      "kind",
-      "amount",
-      "currency"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "kind": {
-        "const": "quantity"
-      },
-      "places": {
-        "description": "How many decimal places the rounding rule keeps; pad to it, never round.",
-        "minimum": 0,
-        "type": "integer"
-      },
-      "unit": {
-        "type": "string"
-      },
-      "value": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "value",
-      "unit"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "kind": {
-        "const": "ratio"
-      },
-      "value": {
-        "description": "A fraction: 0.13 is 13 %.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "value"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "base": {
-        "type": "string"
-      },
-      "kind": {
-        "const": "rate"
-      },
-      "per": {
-        "description": "`per` units of `base` cost `value` units of `quote`.",
-        "type": "string"
-      },
-      "quote": {
-        "type": "string"
-      },
-      "value": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "value",
-      "base",
-      "quote",
-      "per"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "fractional": {
-        "const": true
-      },
-      "grouping": {
-        "const": false
-      },
-      "kind": {
-        "const": "count"
-      },
-      "value": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "value"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "kind": {
-        "const": "code"
-      },
-      "value": {
-        "description": "A token from a fixed list the tool exports; the words for it are the copy key `<tool>.code.<value>`.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "value"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "kind": {
-        "const": "date"
-      },
-      "value": {
-        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "value"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "amount": {
+        "type": "string"
+      },
+      "currency": {
+        "description": "An ISO 4217 code.",
+        "type": "string"
+      },
+      "kind": {
+        "const": "money"
+      }
+    },
+    "required": [
+      "kind",
+      "amount",
+      "currency"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "const": "quantity"
+      },
+      "places": {
+        "description": "How many decimal places the rounding rule keeps; pad to it, never round.",
+        "minimum": 0,
+        "type": "integer"
+      },
+      "unit": {
+        "type": "string"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value",
+      "unit"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "const": "ratio"
+      },
+      "places": {
+        "description": "How many decimal places of the fraction the rounding rule keeps; write the percentage padded to two fewer (0.2820 is 28.20 %), never round.",
+        "minimum": 0,
+        "type": "integer"
+      },
+      "value": {
+        "description": "A fraction: 0.13 is 13 %.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "base": {
+        "type": "string"
+      },
+      "kind": {
+        "const": "rate"
+      },
+      "per": {
+        "description": "`per` units of `base` cost `value` units of `quote`.",
+        "type": "string"
+      },
+      "quote": {
+        "type": "string"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value",
+      "base",
+      "quote",
+      "per"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "fractional": {
+        "const": true
+      },
+      "grouping": {
+        "const": false
+      },
+      "kind": {
+        "const": "count"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "const": "code"
+      },
+      "value": {
+        "description": "A token from a fixed list the tool exports; the words for it are the copy key `<tool>.code.<value>`.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "const": "date"
+      },
+      "value": {
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "const": "identifier"
+      },
+      "value": {
+        "description": "A number that is data, such as a barcode number: write it as it is, keep its leading zeros, never group it.",
+        "pattern": "^[A-Za-z0-9]{1,32}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value"
+    ],
+    "type": "object"
+  }
+]
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only had to add context, and it does: exact decimal-string inputs, refusal-with-reason on anything ambiguous rather than guessing, quoting provenance.source_line in the reply, and passing on the reference-only notice. The gaps left are minor given a full output schema and the declared readOnly/idempotent hints.

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 and the provenance/disclaimer instructions are front-loaded, but the whole payload is written twice, in Chinese and again in English, so the effective length is roughly doubled and much of it repeats the schema's numeric-format description. No sentence is wrong, but a large share of them are duplicates.

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 a full output schema and readOnly/idempotent annotations present, what the description supplies, purpose, input discipline, refusal behavior, provenance quoting, and disclaimer handling, is enough for an agent to call and report results correctly. Only when-to-use routing against the fee and freight siblings is absent.

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 schema already documents rate, price, markup, freight, minimum, currency, quantity, and the rateUnit enum, which sets the baseline at 3. The description adds that values must be exact decimal strings and that unread input is refused, but gives no extra meaning for business fields such as how markup relates to insured amount.

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 names a specific verb and three concrete outputs: computes the CIF insurance premium, the CIF price, and the insured amount, with an optional minimum premium. That is far more specific than the sibling names alone (freight, cbm, fx-convert) and tells an agent exactly which calculation it performs. It never explicitly contrasts itself with those siblings, so it stops short of a 5.

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 is implied by the calculation described, and the text gives input-gathering rules (ask for a required figure, omit an optional one the user did not give). What is missing is when-to-use framing: no statement of when this applies versus a plain freight or duty calculation, and no prerequisites such as needing FOB price plus quantity plus rate.

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

All 出口单 chukoudan toolsInspect
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