Skip to main content
Glama

Forthmatch 3PL Directory

Search the 3PL directory

search_3pl_directory
Read-onlyIdempotent

Use this to find 3PL (third-party logistics) fulfillment providers in the free Forthmatch directory. Filter by the country of the head office or Europe, a service, the store's monthly orders, a listed Shopify integration, or part of the name. Returns up to 50 listings a page with headquarters, warehouse countries, US warehouse states and services, plus each slug for get_3pl_profile. Details come from each company's own website and are unverified unless the company claimed its listing. Claimed listings come first, then the rest by name; it is not a ranking.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_3pl_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPart of the 3PL's name.
pageNo
regionNoHead office anywhere in Europe. Use instead of country.
countryNoCountry of the 3PL's head office: an ISO 3166-1 alpha-2 code such as US, GB, CA, AU, NL or DE, or the English name. Only countries with listings are accepted, and the error lists them. Warehouses can be elsewhere, so check warehouse_countries in the results.
serviceNoOne service the 3PL lists: ecommerce (Ecommerce / DTC), b2b (B2B / wholesale), retail_edi (Retail & EDI), amazon_fba_prep (Amazon FBA prep), cold_chain (Cold chain), hazmat (Hazmat / dangerous goods), kitting (Kitting & assembly), subscription_boxes (Subscription boxes), returns (Returns), international (International / cross-border), freight (Freight), bulky_oversize (Bulky / oversize), apparel (Apparel), health_beauty (Health & beauty), food_beverage (Food & beverage), supplements (Supplements).
monthly_ordersNoThe store's orders per month. Leaves out 3PLs whose checked minimum is higher; listings with no stated or no checked minimum stay in.
shopify_integrationNotrue: only 3PLs that list a Shopify integration.

Output Schema

NameRequiredDescriptionDefault
noteNo
pageYes
totalYes
resultsYes
per_pageYes
directory_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Although the annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), the description adds real behavioral context: results are capped at 50 per page, claimed listings sort first and the order 'is not a ranking', data is self-reported and 'unverified unless the company claimed its listing', and invalid countries produce an error listing the accepted values.

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 front-loaded with the purpose, then the filter set, then the return shape and caveats, with essentially no filler. The latter half packs several facts into long clauses (sorting, provenance, pagination), which makes it dense but still readable.

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?

The description is thorough for a multi-filter search tool: it covers filters, the return fields, page size, ordering, and data provenance, and an output schema already exists to describe the return shape. Only minor items are absent, such as default paging behavior or whether an empty filter set returns everything.

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 high (86%), so most parameter documentation is already present; the description still adds cross-parameter meaning by telling the agent to prefer 'region' over 'country' for European headquarters and by warning that warehouses may sit outside the head-office country, so warehouse_countries in the results must be checked.

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 opens with a concrete verb and resource ('find 3PL fulfillment providers in the free Forthmatch directory') and immediately names the filters it supports, and it distinguishes itself from its sibling by noting it returns 'each slug for get_3pl_profile', so the agent knows that profile details belong to another tool.

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 gives clear conditions for use: filter by head-office country or Europe, by service, monthly orders, Shopify integration, or name; and it explicitly says to use 'region' instead of 'country'. However, it never states when NOT to use this tool (for example, to go straight to a profile or to request quotes), so the guidance stops short of explicitly naming the alternatives.

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.

Resources