Skip to main content
Glama

IFC India Import Duty & Landed Cost

Estimate shipment volume (CBM) from weight

estimate_cbm_from_weight
Read-onlyIdempotent

Gives an approximate shipping volume in cubic metres (CBM) for goods from China from their total gross weight and product type. Use it when the buyer knows the weight but not the CBM. Approximate idea only: if the buyer has the exact CBM from the supplier (packing list), that should be used instead.

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": {
      "weight_kg": "<weight_kg>"
    },
    "name": "estimate_cbm_from_weight"
  }
}

Input Schema

NameRequiredDescriptionDefault
cartonsNoOptional number of cartons; improves the estimate
hs_codeNoOptional Indian HS code (2 to 8 digits) to help pick the product category
productNoProduct name or type, e.g. office chairs, LED lights, garments, bluetooth speakers
weight_kgYesTotal gross weight in kg

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context by flagging the result as approximate and clarifying it is a fallback to authoritative packing-list data. It does not, however, say anything about accuracy range or what happens when product/hs_code are omitted.

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

Conciseness5/5

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

Three tight sentences with zero filler; the output definition is front-loaded, followed by the usage condition and then the exclusion. Every sentence earns its place.

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 read-only estimator with no output schema, the description covers purpose, inputs and the fallback rule adequately. The only gap is that it doesn't characterize the return value (e.g. whether it returns just a number or also a matched category/confidence), which would help since no output schema exists.

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 all four parameters, including that cartons 'improves the estimate' and hs_code's 2-to-8-digit format. The description restates weight and product type but adds no syntax or format detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 (estimates) and resource (shipping volume in CBM), plus the two inputs it derives from (gross weight and product type) and the geographic scope (goods from China). This is clearly distinguishable from siblings like estimate_landed_cost or lookup_hs_code without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names the triggering condition ('when the buyer knows the weight but not the CBM') and the when-not-to-use case with the preferred alternative ('if the buyer has the exact CBM from the supplier (packing list), that should be used instead'). Nothing is left to inference.

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