get_courier
Public profile for one courier by storefront slug or courier id. No PII.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| courier | Yes | Storefront slug or courier UUID |
eurocollis
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must carry behavioral disclosure. 'Public' and 'No PII' indicate a read-safe operation and privacy boundary, but it doesn't cover not-found behavior, auth requirements, or response shape. Satisfactory but minimal.
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 short sentences contain the entire value: what is returned, the identifier criteria, and a privacy note. No filler.
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?
For a single-parameter lookup with no output schema, the description adequately explains the purpose and input. It could be more explicit about the returned profile fields, but the low complexity keeps this from being a major gap.
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% (the 'courier' parameter is described as 'Storefront slug or courier UUID'), and the tool description essentially repeats that. No additional format or validation details are added.
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 uses a specific verb ('get') and resource ('public profile for one courier'), and specifies the two identifier types. 'One courier' distinguishes it from list/search siblings like search_couriers.
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?
Clear context: use when you have a storefront slug or courier ID and need the public profile. No exclusions or references to alternatives, so it isn't a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness4/5
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.