Skip to main content
Glama

select_provider

Evaluate and rank freight intermediaries based on your priority, cargo specialisation, volume, and corridor needs. Receive a recommended provider type and a weighted scorecard to assess real candidates.

Instructions

Choose the right freight INTERMEDIARY — freight forwarder, 3PL/4PL, customs broker, NVOCC or carrier-direct — and know how to grade them. Give a NEED profile (priority cost vs service, cargo specialisation reefer/dangerous-goods/project/e-commerce/high-value, annual volume, corridor count, whether you need warehousing, whether customs is the hard part) and it scores every provider archetype on weighted criteria (corridor coverage, specialisation, technology/visibility, customs depth, cost, service, financial stability), RANKS them, recommends the provider TYPE (+ a pairing, e.g. niche forwarder + customs broker), and emits a weighted SCORECARD you fill in for real candidates. Proves: a reefer-heavy, low-volume, service-led need → a niche cold-chain forwarder tops the rank (NOT a generic mega-3PL); a high-volume cost-led need on a few lanes → carrier-direct / NVOCC; a customs-heavy need pulls in a customs-broker pairing. The criterion weights shift with the need, so the recommendation changes when the profile changes. Honest (regla 7): INDICATIVE archetypes & weights — NOT an endorsement of, or performance claim about, any named provider; run your own RFI/references. PREMIUM: pay per call with x402 (USDC on Base) or a prepaid key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priorityNo'cost' | 'service' | 'balanced' — the primary driver. Optional; default balanced.
specialisationNoCargo specialisation needed: 'reefer' / 'dangerous-goods' / 'project' / 'ecommerce' / 'high-value' / 'none'. Optional; default none.
cargo_typeNoAlias for 'specialisation' — a free-text cargo description is parsed into a specialisation. Optional.
annual_containersNoAnnual container volume (rough) — sets the volume band (low <50, mid, high ≥500). Optional.
corridor_countNoNumber of distinct corridors/regions you ship. Optional; default 1.
needs_warehousingNoDo you need warehousing/fulfilment, not just transport? Pulls toward 3PL/4PL. Optional.
customs_heavyNoIs customs the hard part (high-duty, regulated, FTA-heavy)? Pulls in a customs broker. Optional.
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 discloses behavior: scoring archetypes, ranking, recommending type+pairing, and emitting a scorecard. It also includes honesty disclaimers about the indicative nature and premium payment.

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 well-structured with clear sections: purpose, usage, examples, honesty note, premium. It front-loads key information, though slightly verbose; each sentence adds value.

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 7 parameters (none required) and no output schema, the description covers the decision logic, input effects, and output deliverables (scorecard). It lacks detail on exact output format but is otherwise 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?

The schema has 100% parameter description coverage, so baseline is 3. The description adds significant value by explaining how parameters like specialisation and volume affect the ranking, providing context beyond the schema definitions.

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 defines the tool's purpose: selecting and grading freight intermediaries. It uses specific verbs ('choose', 'grade') and resource ('freight INTERMEDIARY'), and distinguishes from sibling tools like carrier_recommendation by focusing on intermediary archetypes rather than specific carriers.

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 when to use the tool: when you need to choose an intermediary type based on a needs profile. It provides explicit context through examples (e.g., reefer-heavy need leads to a niche forwarder), but does not explicitly state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Baneado98/freight-pulse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server