carrier_reliability
On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| carrier_code | Yes | Carrier SCAC, e.g. MAEU |
ocean-schedules
TDQS
C2.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description lacks behavioral details such as return format, pagination, or authentication requirements. It only vaguely mentions 'on-time performance and delay distribution'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, but it includes inaccurate information (optional lane) that wastes space. It could be concise if corrected.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/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 should explain return values. It does not. The tool is incomplete for an agent to understand what data it will receive.
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?
The single parameter 'carrier_code' has 100% schema coverage with a description. The tool description adds no extra meaning beyond the schema, but the misleading reference to an optional lane degrades clarity. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states on-time performance and delay distribution for a specific carrier, but the mention of an optional lane is misleading because the input schema does not include a lane parameter. This inaccuracy undermines clarity.
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 is provided on when to use this tool versus sibling tools like 'carrier_league' or 'compare_lanes'. The description does not explain context or exclusions.
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
A3.5/5.0
Disambiguation5/5
Each tool targets a distinct aspect of ocean shipping: storms, carrier performance, lane schedules, port conditions, and alerts. Even overlapping areas like carrier reliability and lane comparisons are clearly differentiated by scope and purpose.
Naming Consistency4/5
All tools use consistent snake_case naming. Most follow a verb_noun or noun_noun pattern, though some start with verbs (e.g., compare_lanes, find_sailings) and others with nouns (e.g., carrier_league, port_congestion). This is predictable but not perfectly uniform.
Tool Count5/5
With 12 tools, the server is well-scoped for the domain of ocean scheduling. Each tool provides meaningful functionality without redundancy, covering storms, carriers, lanes, ports, and alerts.
Completeness4/5
The tool surface covers core information needs: storms, carrier reliability, lane schedules, port congestion, transit times, and alerts. Minor gaps exist, such as lacking detailed vessel info or carrier-specific data beyond reliability, but the overall coverage is strong for an informational service.