Skip to main content
Glama

Triplicate – export documents

Calculate CBM and chargeable weight

calculate_shipment
Read-only

Use when a user has carton sizes and quantities and asks for the CBM, the chargeable weight, LCL revenue tons or whether the volume fits a 20ft, 40ft or 40ft high cube container. From carton sizes, quantities and gross weights: total CBM, gross weight, air and express volumetric and chargeable weight, LCL revenue tons and which standard containers the volume fits.

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": {
      "cartons": "<cartons>"
    },
    "name": "calculate_shipment"
  }
}

Input Schema

NameRequiredDescriptionDefault
cartonsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value by disclosing that the tool computes a specific battery of derived figures (volumetric vs chargeable weight, revenue tons, container-fit across three standard sizes), which tells the agent what to expect back beyond a generic 'calculation'.

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?

Two sentences, front-loaded with the usage condition followed by the output inventory — no filler. The second sentence is a dense list that borders on restating the title's territory, but every item is a distinct computed value an agent needs.

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?

There is no output schema, so the description must describe return values — and it does so thoroughly, listing all six computed outputs. The remaining gap is minor: it doesn't mention unit conventions for inputs or edge cases (zero quantity, missing gross weight), which for a nested carton array would be useful.

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 0%, so the description must carry parameter meaning; it partially does by naming 'carton sizes, quantities and gross weights', which maps onto length/width/height, quantity and gross_weight_kg. However, it never states units or that gross weight is per single carton (only the nested schema does), so the compensation is incomplete for a nested-array parameter.

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

Purpose5/5

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

States a specific verb-and-resource ('Calculate CBM and chargeable weight') and enumerates the exact quantities produced: total CBM, gross weight, volumetric/chargeable weight, LCL revenue tons, and container fit. This is clearly distinguishable from siblings like calculate_export_price, which the description never overlaps with.

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 gives a concrete trigger: 'Use when a user has carton sizes and quantities and asks for the CBM, the chargeable weight, LCL revenue tons or whether the volume fits a 20ft, 40ft or 40ft high cube container.' It doesn't name an alternative tool or state when-not-to-use, but the input-condition + question-type framing is stronger than typical implied usage.

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