Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

快递体积重(抛重)计算

volume-weight

快递体积重(抛重)计算:输入长宽高与抛比,算体积重。发货前预判计费重、避免运费超预算。抛比按承运方实际填写,不内置某家公司规则。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "lengthCm": "<lengthCm>",
      "widthCm": "<widthCm>",
      "heightCm": "<heightCm>"
    },
    "name": "volume-weight"
  }
}

Input Schema

NameRequiredDescriptionDefault
divisorNo可选:抛比,默认 6000
widthCmYes宽(cm)
heightCmYes高(cm)
lengthCmYes长(cm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full disclosure burden. It does disclose key traits: it uses the divisor supplied by the caller and does not embed any carrier's rules, and it returns a deterministic result plus its basis. It does not describe error handling for missing or zero values, rounding behavior, or how the result differs from chargeable weight, which the usage sentence invokes but never defines.

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

Conciseness4/5

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

The description is front-loaded with purpose, followed by use context and a constraint. The final sentence about model arithmetic instability is meta-commentary rather than tool specification, a small amount of filler.

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?

For a four-parameter pure calculation, the definition covers inputs, output nature (deterministic result plus basis), and the constraint against built-in carrier rules. Missing are rounding/precision and validation behavior, which matter somewhat for a billing-adjacent calculator.

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 all four parameters are already documented in the schema, including the divisor's default value of 6000. The description reinforces that the divisor is caller-supplied and carrier-specific, but adds no units, bounds, or format details beyond what the schema provides.

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 delivers a concrete verb and resource: it inputs length, width, height and a divisor, and computes volumetric (抛重) weight. It is unambiguous for a single-purpose calculator. No sibling tool performs a similar calculation, so the lack of explicit differentiation is a minor gap.

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?

It states a clear context for when to use the tool: pre-shipment estimation of billable weight to avoid blowing the freight budget. It also explains that this tool is preferred when the agent's own arithmetic is unreliable. However, it gives no explicit when-not guidance or comparison to alternatives.

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