Skip to main content
Glama

Forthmatch 3PL Directory

Get a 3PL profile

get_3pl_profile
Read-onlyIdempotent

Use this for the full directory profile of one 3PL: head office, description, warehouse countries and named locations, US states, services, industries, Shopify integration, stated minimum orders and pricing where published, listing status, the pages the details were taken from, and similar listings. Pass the slug from search_3pl_directory, or the last part of a forthmatch.io/3pl-directory/ URL.

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": {
      "slug": "<slug>"
    },
    "name": "get_3pl_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe listing's slug, for example shipbob.

Output Schema

NameRequiredDescriptionDefault
nameYes
slugYes
detailsNo
sourcesNo
sectionsNo
descriptionNo
profile_urlYes
alternativesNo
headquartersNo
quote_form_urlYes
warehouse_locationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so safety is covered. The description adds meaningful behavioral context by listing what the profile contains and flagging that minimum orders and pricing are only present 'where published', warning the agent that some fields may be absent.

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?

Two sentences, front-loaded with the intended use, with no filler. The long field enumeration is dense but each item helps an agent judge whether the profile answers its question, though it could be trimmed slightly.

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?

With a single required parameter, an output schema, and full annotation coverage, the definition is essentially complete; the description even previews the return payload. Only minor gaps remain, such as what happens when a slug is unknown.

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% and the slug pattern plus example are already documented in the schema. The description still adds value by explaining where the slug comes from — a search result or the trailing segment of a directory URL — which the schema does not say.

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 specific verb and resource ('full directory profile of one 3PL') and then enumerates the fields returned, so an agent knows exactly what the tool produces. It also implicitly separates itself from search_3pl_directory by positioning that sibling as the source of the slug input.

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?

It states the use case ('full directory profile of one 3PL') and gives concrete workflow guidance: obtain the slug from search_3pl_directory or from a forthmatch.io/3pl-directory/<slug> URL. There is no explicit when-not guidance, but the single-listing scope makes the boundary against the search sibling fairly evident.

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