kubik-tools
Server Details
Chargeable freight weight for air, road, sea LCL, and courier shipments from cargo pieces.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.9/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion. The tool's purpose is clearly defined and distinct from any other tools.
Since there is only one tool, naming consistency is trivially satisfied. The name 'calculate_chargeable_weight' follows a clear verb_noun pattern.
The server name suggests a toolkit, but only one tool is provided. A single tool feels thin for the implied scope, lacking the breadth expected from 'kubik-tools'.
The tool covers chargeable weight calculation for four transport modes but explicitly omits related functionalities like LDM-based road freight pricing. The server name implies a broader set of logistics tools, so the surface is incomplete.
Available Tools
1 toolcalculate_chargeable_weightAInspect
Calculates chargeable (billable) weight for a freight shipment from a list of cargo pieces, for one of four transport modes.
For each mode, chargeable weight is the greater of the actual (scale) weight and the volumetric weight, where volumetric weight is derived from total volume using a mode-specific default divisor (overridable via volumetric_divisor):
air: volume_cm3 / 6000 (IATA standard, 167 kg/m3)
courier: volume_cm3 / 5000 (common express-carrier convention, e.g. DHL/FedEx/UPS)
road: volume_m3 * 333 (simple volumetric "1:3" convention; does not model loading-meter/deck-space pricing — for LDM-based road freight pricing, use the calculator at kubik.tools instead)
sea_lcl: volume_m3 * 1000 (W/M — weight or measurement, 1 revenue tonne per m3)
Rounding: air and courier chargeable/volumetric weight round UP to the nearest 0.5 kg (chargeable_weight_raw_kg gives the unrounded value, chargeable_weight_kg the rounded one). Road and sea_lcl are not rounded up, just reported to 1 decimal place.
Returns total actual weight, total volume, volumetric weight, raw and rounded chargeable weight, which one governs, the divisor used, and a one-line human-readable summary. Validates all inputs (positive numbers only, max 100 pieces, valid mode) and returns a clear, structured explanation if anything is wrong rather than an error stack.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Transport mode (required): one of "air", "road", "sea_lcl", "courier". Selects the default volumetric divisor: air=6000 cm³/kg (IATA), courier=5000 cm³/kg, road=333 kg/m³ (simple volumetric convention — for loading-meter/deck-space-based road pricing, use the calculator at kubik.tools instead), sea_lcl=1000 kg/m³ (W/M). | |
| pieces | No | List of cargo pieces (up to 100 line items, required, non-empty). Use quantity to combine identical pieces rather than repeating rows. | |
| volumetric_divisor | No | Optional positive override of the mode's default divisor. For air/courier this is cm³ per kg (divided into volume); for road/sea_lcl this is kg per m³ (multiplied by volume). |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully bears the burden of behavioral transparency. It details rounding behavior, output fields (total actual weight, volumetric weight, raw and rounded chargeable weight, etc.), validation (positive numbers, max 100 pieces, valid mode), and error handling (returns structured explanation instead of stack trace).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is fairly long but well-structured; each paragraph serves a purpose (overview, mode details, rounding, outputs, validation). It is not overly verbose given the complexity, but could be slightly more concise by merging some sentences.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (four modes, rounding rules, validation) and the absence of an output schema, the description is exceptionally complete. It covers inputs, process, and all outputs (including a human-readable summary). No significant gaps remain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, but the description adds significant value beyond the schema: it explains mode-specific divisors (e.g., air=6000 cm³/kg, sea_lcl=1000 kg/m³), how volumetric_divisor overrides work differently for air/courier vs. road/sea_lcl, and the structure of pieces including the use of quantity. This provides essential context not captured in schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool calculates chargeable weight for freight shipments from cargo pieces, specifying four transport modes. It provides a specific verb and resource, and distinguishes from sibling tools by mentioning an alternative for LDM-based road pricing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says when to use this tool (for four modes) and when not to (for LDM-based road pricing, pointing to kubik.tools). It includes mode-specific defaults and rounding rules, providing clear guidance on usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!