Skip to main content
Glama

AI Fusion One

Supplier matching

supplier_matching

Candidate manufacturers/suppliers for a product or category requirement, from Wikidata manufacturer and industry/product relations, with curated categories for robotics, drones/UAV, industrial machinery and sensors/IoT (optional sector and country filters). Source-attributed and confidence-scored; no prices or stock. PAID tool: call without x402_payment to get the payment requirements. Price: $0.25 per call. Paid in REAL USDC on Base mainnet (chain 8453) via x402.

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": {
      "requirement": "<requirement>"
    },
    "name": "supplier_matching"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax candidates.
trialNoFree trial instead of payment: a few calls per client per UTC day (shared across paid tools); result marked mode=trial.
sectorNoOptional sector for curated category mapping.
countryNoOptional ISO alpha-2 country filter (Wikidata country).
requirementYesProduct or category requirement, e.g. 'stainless steel water bottle manufacturers'.
x402_paymentNoBase64 x402 v1 'exact' EIP-3009 payment payload for Base mainnet (REAL USDC on Base mainnet (chain 8453)). Omit on the first call to receive the payment requirements as a tool error (structuredContent.accepts); sign them and call again with this argument. One payment funds exactly one call.

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?

Adds substantial behavior beyond the annotations: it is a paid tool at $0.25/call settled in real USDC on Base mainnet, the first call without payment returns requirements as a structured error, one payment funds exactly one call, and trial mode is rate-limited per client per UTC day and flagged mode=trial. It also discloses output character (source-attributed, confidence-scored). The only gap is that readOnlyHint=false sits oddly on a lookup tool and the description never explains why the call is framed as non-read-only, leaving a small ambiguity about side effects.

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-loaded with the core capability, then pricing and payment mechanics follow in priority order, which matches what an agent needs before calling. The opening sentence is a dense run-on with nested parentheticals that takes a second read, and the price is stated twice (once as $0.25, once implicitly via 'one payment funds exactly one call'), but no sentence is truly wasteful.

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 no output schema, the description carries the burden of describing returns and does so at a high level (source-attributed, confidence-scored candidates, mode=trial marker) while setting expectations that price/stock are absent. For a six-parameter, payment-gated discovery tool this is close to complete; only the response envelope and the effect of limit on result quality remain unspecified.

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 already 100%, so the baseline is 3; the description earns a 4 by explaining how x402_payment is meant to be used in sequence (omit first, then sign and resend) and by framing sector and country as optional narrowing filters. It does not explain how limit interacts with cost or whether sector changes ranking, but it adds real meaning over the schema text.

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?

Names a specific resource (candidate manufacturers/suppliers) for a specific input (product or category requirement) and states the data source (Wikidata manufacturer and industry/product relations) plus curated categories. Nothing in the sibling list overlaps, so an agent can route to it unambiguously from the name alone.

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?

Gives a clear use context and an explicit exclusion ('no prices or stock'), which steers an agent away from using it for pricing or availability questions. It also documents the paid-call flow (call without x402_payment to get requirements, then retry) and a trial escape hatch. It falls short of 5 because it never contrasts against a named alternative source or states what to do when Wikidata coverage is thin.

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