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.
Last updated
16
MIT
Adopte un Conteneur - Container Delivery & Dimensions
Server Details
Delivery cost calculator and container dimensions for France. Real HT/TTC prices.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- adopteunconteneur/mcp-container-delivery
- GitHub Stars
- 0
- Server Listing
- Adopte un Conteneur — Container Delivery Calculator
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
A3.9/5.0
Tool DescriptionsA
Average 4/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
The two tools have completely distinct purposes: one calculates delivery costs, the other retrieves dimensions. No overlap.
Naming Consistency5/5
Both use a consistent verb_noun camelCase pattern (calculate... and get...), which is clear and predictable.
Tool Count3/5
Two tools is minimal but acceptable for a narrowly focused server on container delivery and dimensions. It feels somewhat thin but not unreasonable.
Completeness3/5
The tools cover the core functions implied by the server name (cost calculation and dimension lookup), but lack additional operations like listing depots or placing orders, leaving minor gaps.
Available Tools
2 toolscalculateContainerDeliveryCostAInspect
Calcule le coût de livraison d'un ou plusieurs conteneurs maritimes vers une adresse en France. Sélectionne automatiquement le dépôt le plus économique et retourne le prix réel HT et TTC.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| quantity | Yes | Nombre de conteneurs à livrer | |
| container_type | Yes | Type de conteneur : 20ft, 40ft ou 40ft_hc (High Cube) | |
| delivery_address | Yes | Adresse complète ou ville de livraison en France |
Tool Definition Quality
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses automatic depot selection and return of HT/TTC prices. No annotations provided, so description partially covers behavioral traits. Lacks details on potential side effects, authorization needs, or completeness of price calculation.
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?
Two sentences efficiently convey purpose and key behavior. No redundant information.
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?
Given no output schema, description hints at return fields (HT/TTC). Parameters are simple and well-documented. Could specify address format or currency, but overall adequate for a straightforward cost calculation tool.
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 covers all 3 parameters (100%). Description reiterates them in context but adds no extra semantic value beyond the schema definitions. Baseline score of 3 applies.
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?
Clear verb 'calcule le coût de livraison' with specific resource 'conteneurs maritimes vers une adresse en France'. Distinct from sibling 'getContainerDimensions' which focuses on dimensions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. Does not specify prerequisites (e.g., address format) or when not to use it. Only describes the core function.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
getContainerDimensionsAInspect
Retourne les dimensions intérieures et extérieures, volumes, surfaces et poids des containers. Permet de filtrer par type (stockage, dry, high_cube, reefer), taille (6ft à 45ft), volume minimum ou surface minimum. Inclut les surfaces combinées pour plusieurs containers accolés.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| size | No | Taille du container en pieds. Omis = toutes les tailles. | |
| type | No | Type de container. Omis = tous les types. | |
| quantity | No | Nombre de containers accolés (2, 3 ou 4) pour obtenir la surface combinée. Nécessite size=20ft ou size=40ft. | |
| min_volume_m3 | No | Volume intérieur minimum en m³ (ex: 30 pour trouver un container d'au moins 30m³) | |
| min_surface_m2 | No | Surface intérieure minimum en m² (ex: 13 pour trouver un container d'au moins 13m²) |
Tool Definition Quality
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It clearly indicates the tool returns data (retourne) and mentions constraints like quantity needing size 20ft or 40ft. It does not discuss authentication or rate limits, but the read-only nature is implied.
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 and covers the main functionality in a few sentences. It is well-structured, but could be slightly more organized by separating filter options from output details.
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?
Given no output schema, the description adequately describes the return values (dimensions, volumes, surfaces, weights) and parameters. It could be more explicit about the output format (e.g., list of containers) but is generally complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but the description adds context such as using quantity for combined surfaces and requiring specific sizes. It also explains the purpose of volume and surface filters with examples.
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 it returns dimensions, volumes, surfaces, and weights of containers, with filtering by type, size, volume, and surface. It also mentions combined surfaces for multiple containers. This clearly distinguishes it from the sibling tool for delivery cost.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains filtering options and the quantity parameter's requirement for specific sizes. However, it does not explicitly state when to use this tool versus the sibling tool, though the sibling's purpose is distinctly different.
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
- AlicenseBqualityCmaintenanceCompare parcel and letter delivery prices across 60+ carriers in 27 European countries.Last updated1MIT
- Alicense-qualityAmaintenanceCalculates total landed cost of international payments including FX spread, transfer fees, and settlement time across multiple payment methods, and provides free currency conversion and ECB exchange rates.Last updatedMIT
- FlicenseBqualityDmaintenanceEnables AI assistants to calculate French individual income tax and retrieve current tax brackets using official government data. Supports household composition calculations and provides up-to-date tax information for French residents.Last updated1114
Try in Browser
Your Connectors
Sign in to create a connector for this server.