Skip to main content
Glama

BRAINIAC Freight & Customs

Calculate shipment weight and volume

freight-customs_shipment-weight-volume-calculate

Sum supplied package weights and calculate volume from centimetre dimensions. Volumetric weight is calculated only when the request includes a divisor. Price $0.03 USDC. POST /api/v1/freight-customs/shipment-weight-volume-calculate. Unpaid calls return 402 and do not run.

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": {
      "packages": "<packages>"
    },
    "name": "freight-customs_shipment-weight-volume-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
packagesYes
statedVolumeM3No
statedNetWeightKgNo
volumetricDivisorNo
statedGrossWeightKgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does reasonably well: it discloses the conditional branch (volumetric weight only when a divisor is supplied), the cost ($0.03 USDC), and that unpaid calls return 402 without executing. That payment-gate behavior is exactly the kind of operational detail an agent needs before invoking. It does not describe the response shape or rounding/units of the computed result.

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?

Four short sentences with the functional behavior front-loaded before the commercial and transport details. Every sentence carries information (computation, conditional branch, price, endpoint, failure mode). The endpoint path largely restates the tool name, which is minor waste.

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 stateless calculation tool with no output schema and no annotations, the description covers what it computes, when a branch triggers, what it costs, and how failure behaves. The remaining gap is what the response contains and how the stated* inputs are treated, which matters given five undocumented parameters.

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 compensate, and it only partially does. It clarifies weight summation, centimetre dimension input, and the role of the divisor, which maps to the packages and volumetricDivisor parameters. It says nothing about count, the stated* parameters (statedVolumeM3, statedNetWeightKg, statedGrossWeightKg), or how stated values interact with computed ones — likely the most consequential ambiguity in the schema.

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 opens with a specific verb and resource: sum package weights and calculate volume from centimetre dimensions. An agent immediately knows this is a deterministic calculation tool, not a validation or extraction tool like the sibling document-* tools. It falls short of a 5 only because it never explicitly contrasts itself with those siblings.

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 semantics, and the divisor sentence implicitly tells the agent when volumetric weight will be produced. However, there is no explicit when-to-use statement, no guidance on when to call this versus packing-list-validate or shipment-document-consistency, and no stated prerequisites beyond payment.

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