Published courier storefront with its canonical URL (custom domain / subdomain / platform path) and corridor pages. Omit slug to list storefronts.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | ||
| limit | No | Used when listing |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It usefully discloses that only published storefronts are returned, that output includes canonical URL and corridor pages, and that omitting the slug switches to list mode. It does not cover pagination, errors, or authentication, but the core behavior is transparent.
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 two compact sentences with no filler: the first defines what is returned, the second explains the key usage rule. Every sentence earns its place.
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?
For a simple optional-parameter get/list tool, the description names the main return fields and the listing mode, but with no output schema or annotations it leaves gaps around the exact listing response shape, limit handling, and pagination. It is adequate but not fully complete.
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?
The slug parameter has no schema description, so 'Omit slug to list storefronts' provides essential semantic value by explaining that the parameter toggles between single-get and list behavior. The limit parameter is only minimally described in the schema, and the description reinforces its listing context but does not add defaults or bounds.
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 identifies the specific resource—'published courier storefront'—and its key output fields (canonical URL and corridor pages), and the name 'get_storefront' supplies the verb. It is distinguishable from sibling 'get_courier', though it does not explicitly name that sibling.
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 instruction 'Omit slug to list storefronts' gives a clear conditional usage rule. However, there is no explicit guidance on when to prefer this tool over siblings like get_courier or search_couriers, so the usage context is only partially stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action: reference data, pricing, customs, courier discovery, storefronts, and tracking. Even closely related tools like get_courier, get_storefront, and search_couriers are clearly separated by function.
All tool names follow a consistent imperative verb_noun snake_case pattern. The get_ prefix is used for lookups, while convert_, estimate_, search_, and track_ clearly signal different actions.
Twelve tools is well within the ideal range, and each tool covers a distinct operational need for the EuroCollis pre-booking and tracking workflow. There is no obvious redundancy or bloat.
The set covers routes, cities, services, prohibited items, quotes, customs estimates, currency conversion, courier discovery, storefronts, and tracking, so nearly all public user intents are supported. Minor gaps remain around explicit supported-country/currency lists and the final booking step, but agents can work around these via get_routes and get_eurocollis_info.