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.
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.5/5 across 1 of 1 tools scored.
Only one tool exists, so no risk of confusion with other tools. The single tool's purpose is clearly defined.
With a single tool, naming is inherently consistent. The name 'calculate_cbm' follows a clear verb_noun pattern.
One tool is appropriate for a focused CBM calculator server. It handles all necessary calculations without splitting into multiple tools, though a very small set could be considered slightly thin.
The tool covers all core functionality: calculating volume in CBM and CFT, total weight, and container fit assessment. No obvious gaps for its intended 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.
| 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
| Name | Required | Description |
|---|---|---|
| totalCbm | Yes | |
| totalCft | Yes | |
| containers | Yes | |
| calculatorUrl | Yes | |
| totalWeightKg | Yes | |
| totalWeightLbs | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and idempotentHint=true, so no write behavior is expected. The description adds value by detailing the output (CBM, CFT, weight, fill percentage, overload flag) and input unit flexibility (metric/imperial). No behavioral contradictions with annotations.
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 three sentences, front-loaded with the main purpose, and no redundant information. Every sentence adds value: first sentence states function, second lists use cases, third describes inputs and outputs.
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 tool has two parameters (both documented), a listed output schema, and annotations, the description sufficiently covers input handling (metric/imperial) and output (CBM, CFT, weight, container fill). It also mentions the overload flag, providing complete context for an agent.
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 coverage is 100%, with descriptions for each parameter. The description reinforces the meaning of 'items' and 'unitSystem' by explicitly stating the units (cm/kg or in/lb) and connecting them to the output. This adds context beyond the schema's minimal 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 explicitly states the tool calculates shipment volume (CBM, CFT), total weight, and container fit. It uses specific verbs ('calculate', 'fit') and clearly identifies the resources (shipment, containers). No siblings exist, but the tool is well-differentiated from any unrelated tools by its unique function.
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 provides a comprehensive list of usage scenarios (e.g., 'how much space a shipment takes', 'whether cargo will fit in a container'). It does not explicitly mention when not to use it, but the specificity of the use cases is sufficient. Lacks a direct contrast with alternative tools, but there are no sibling tools.
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!