A
license-
qualityC
maintenancePlan optimal container & truck loads: 3D layouts, right-size the container mix, and check utilization, centre of gravity, crush protection and securing across 200+ equipment types.
17
MIT
cbm
Server Details
Calculate shipment volume (CBM/CFT), weight, and how cargo fits standard shipping containers.
- 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.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A4.5/5.0
Tool DescriptionsA
Average 4.4/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no ambiguity or overlap with other tools. The tool's purpose is clearly defined.
Naming Consistency5/5
The single tool name 'calculate_cbm' follows a clear verb_noun pattern, which is consistent and descriptive.
Tool Count4/5
Having a single tool for a very specific calculation service is slightly below the ideal range but still appropriate, as the server's scope is intentionally narrow.
Completeness5/5
The tool fully covers its intended domain of CBM and container fill calculations, leaving no obvious gaps for its stated purpose.
Available Tools
1 toolcalculate_cbmCalculate CBM & Container FitARead-onlyIdempotentInspect
Calculate total shipment volume (CBM / cubic metres and CFT / cubic feet), total weight, and how that cargo fits into standard shipping containers (20ft Standard, 40ft Standard, 40ft High Cube). Use this whenever someone asks how much space a shipment takes, how many cubic metres or CBM their boxes / pallets / cartons add up to, whether cargo will fit in a container, what container size they need, or how full a container will be. Accepts a list of items with length, width, height, weight and quantity in metric (cm, kg) or imperial (in, lb) units; returns total CBM, CFT, total weight, and per-container fill percentage with an overload flag.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | The cargo line items to total up. | |
| unitSystem | No | Units for the item dimensions and weight. 'metric' = centimetres and kilograms; 'imperial' = inches and pounds. | metric |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| totalCbm | Yes | |
| totalCft | Yes | |
| containers | Yes | |
| calculatorUrl | Yes | |
| totalWeightKg | Yes | |
| totalWeightLbs | Yes |
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds useful return details (total CBM, CFT, weight, fill percentage, overload flag) that go beyond annotations, though it doesn't mention any constraints on side effects.
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 concise, three sentences front-loaded with the purpose. It avoids redundancy and uses efficient wording. Could be slightly more structured (e.g., separated use cases), but overall effective.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (multi-unit calculation with container fitting), the description explains all return values (CBM, CFT, total weight, fill percentage, overload flag). Combined with full schema coverage and annotations, it is complete.
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 baseline is 3. The description reiterates that items have length, width, height, weight, quantity in metric or imperial units, but adds no new semantic information beyond what the schema already provides.
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?
The description clearly states the tool calculates total shipment volume (CBM, CFT), total weight, and container fit. The verb 'calculate' and resource 'CBM & Container Fit' are specific, and since there are no sibling tools, no differentiation is needed.
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?
The description explicitly lists when to use the tool, including queries about shipment space, cubic metres/CFT, container fit, and container size. It provides clear context without needing exclusions or alternatives.
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!
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to plan container and truck loads from plain-English shipment descriptions, returning fitted containers, utilization, non-fitting items, and interactive 3D load plans.195MIT
- AlicenseAqualityAmaintenanceAI agent access to 11 freight calculation and reference tools — LDM, CBM, chargeable weight, pallet fitting, ADR dangerous goods (2,939 entries), airline codes (6,352), HS codes (6,940), INCOTERMS, container specs, unit converter, and ADR 1.1.3.6 exemption calculator.241,3854MIT
@kubova/mcpofficial
AlicenseAqualityCmaintenanceLets AI agents pack shipping containers using the Kubova calculator, with tools for container loading and API key verification.420MIT