Skip to main content
Glama

Forthmatch 3PL Directory

Request 3PL quotes

request_3pl_quotes

Use this when the person asks you to get 3PL fulfillment quotes for their online store. It sends one request to Forthmatch, which forwards it to providers from its free directory that fit the order volume and region, and each provider replies to the person by email. Forthmatch is not a 3PL and does not quote itself. No account, nothing to pay. Only call it after the person has agreed and given the email address providers should reply to: the email and store details go to those providers. Set provider_slug when they are asking about one listed 3PL. Limits: 5 per 10 minutes per email address and per IP address, and 5 an hour per IP address.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>",
      "store_url": "<store_url>"
    },
    "name": "request_3pl_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe requester's email. Providers reply to this address.
needsNoWhat the store needs: b2c (B2C fulfillment), b2b (B2B or wholesale), returns (Returns), kitting (Kitting), cold_chain (Cold chain), fba_prep (FBA prep), other (Other).
notesNoAnything else providers should know: SKUs, order size, timing.
marketsNoMain countries the orders go to.
ship_fromNoCountry or region the stock should ship from.
store_urlYesThe online store, for example yourstore.com.
provider_slugNoSlug of one listed 3PL the person is asking about, if any.
monthly_ordersNoOrders per month: under_500 (Under 500), 500_2000 (500 to 2,000), 2000_10000 (2,000 to 10,000), over_10000 (Over 10,000).

Output Schema

NameRequiredDescriptionDefault
sentYes
messageYes
reply_toNo
asking_aboutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds what those hints cannot: third-party emails are sent on the user's behalf, their email and store details are disclosed to providers, no account is needed, and nothing is charged. It also discloses concrete rate limits (5 per 10 minutes per email and IP, 5 per hour per IP), which is exactly the kind of operational constraint an agent needs before calling.

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?

Front-loads the use case, then explains the mechanism, then the precondition, then the limits, so the most decision-relevant content comes first. Every sentence carries information, though the description is dense and the limits sentence packs several distinct constraints without separation.

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 the outward-facing side effects, data disclosure, consent precondition, and rate limits for an 8-parameter tool that contacts third parties. Because an output schema exists, the description does not need to explain return values, and the remaining parameters are fully documented in the schema.

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 the baseline is 3, but the description adds meaning beyond the schema by tying the email parameter to the reply channel and giving a rule for when to set provider_slug ('when they are asking about one listed 3PL'). Optional fields like needs, markets and monthly_orders are left to the schema, which already enumerates them.

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?

States a specific verb and resource ('get 3PL fulfillment quotes') and clarifies the mechanism: one request to Forthmatch forwarded to directory providers. It also explicitly says Forthmatch is not a 3PL and does not quote itself, which distinguishes this tool from get_3pl_profile and search_3pl_directory.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ('Only call it after the person has agreed and given the email address providers should reply to') and a conditional routing rule for the provider_slug parameter. It also names the situation that selects this tool (the person asks for quotes for their online store), so an agent can distinguish it from browsing the directory.

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