Skip to main content
Glama

ShippingRates MCP Server (Apify)

by actor.apify.vinaybhosle--shippingrates-mcp

Get CFS Handling Tariffs

shippingrates_cfs_tariffs
Read-onlyIdempotent

Get Container Freight Station (CFS) handling tariffs — charges for LCL (Less than Container Load) cargo consolidation and deconsolidation at port warehouses.

Use this for LCL shipments to estimate warehouse handling costs. Returns per-unit handling rates, minimum charges, and storage fees at the specified port. Not relevant for FCL (Full Container Load) shipments.

PAID: $0.05/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions.

Returns: Array of { facility, service_type, cargo_type, rate_per_unit, unit, minimum_charge, currency }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portYesUN/LOCODE port code (e.g. INMAA, INMUN)
serviceNoFilter by service type
x_paymentNox402 payment proof header
cargo_typeNoFilter by cargo type

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses payment requirement ($0.05/call via x402) and 402 error response. Annotations already indicate readOnly and idempotent, but description adds critical cost and error behavioral context.

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?

Three concise paragraphs: definition, usage guidance, payment/return format. No unnecessary sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage, return format (no output schema), and payment. Complete and self-contained.

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%, so baseline 3. Description adds value by explaining port parameter with examples and the return structure, but does not detail all parameters beyond schema.

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?

Clearly states it retrieves CFS handling tariffs for LCL shipments, distinguishing from FCL. Specific verb 'get' and resource 'CFS handling tariffs'. Sibling differentiation by excluding FCL.

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?

Explicitly says use for LCL shipments to estimate warehouse costs, and not relevant for FCL. Provides clear context but does not name specific alternative tools among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ShippingRates MCP Server (Apify) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

All 26 tools have clearly distinct purposes, with detailed descriptions that differentiate overlapping areas (e.g., transit vs. schedule vs. vessel schedule). Even closely related tools like dd_calculate, dd_compare, and dd_countdown are well-delineated.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with prefix 'shippingrates_'. Compound names use underscores predictably (e.g., dd_calculate, inland_compare, vessel_schedule_options), making the naming scheme highly predictable.

Tool Count4/5

26 tools is slightly above the ideal range, but the breadth of features (rates, D&D, inland, congestion, risk, schedules, etc.) justifies the count. Each tool earns its place, and there is minimal bloat.

Completeness5/5

The tool set covers all major aspects of shipping intelligence: rates, surcharges, local charges, D&D, inland haulage, congestion, risk, transit, schedules, regulatory updates, and discovery tools. No obvious gaps for the stated purpose.

Resources