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. TESTNET ONLY: priced in Base Sepolia test USDC (no real value).

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 Sepolia (TESTNET test USDC, no real value). 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.2/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, openWorld=true, idempotent=false), the description discloses the critical behavioral facts an agent could not infer: it is a PAID tool at $0.25 per call, the first call intentionally errors to return payment requirements, and it runs on Base Sepolia test USDC with no real value. It also characterizes the output as source-attributed and confidence-scored, and rules out price/stock data.

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?

It is a single dense paragraph that front-loads what the tool returns before the payment mechanics, and every sentence carries information (scope, source, filters, price, testnet warning). The heavy parenthetical nesting makes it slightly harder to scan but nothing is redundant.

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 six parameters and no output schema, the description carries the return-value burden and does so partially by stating results are source-attributed and confidence-scored, and it covers the top-level payment lifecycle and trial mode. It does not sketch the actual response shape or candidate fields, which is a modest gap for a discovery tool with no output 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; the description earns above that by explaining that the four sector enum values map to curated category sets and that country filters on the Wikidata country field, which adds meaning beyond the bare enum list. The payment payload mechanics are also contextualized in prose, though the field-level syntax remains schema-only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely ('Candidate manufacturers/suppliers for a product or category requirement'), the underlying source (Wikidata manufacturer and industry/product relations), the curated domain coverage, and explicitly excludes prices/stock. It reads as a noun phrase rather than a verb+resource statement and never names a sibling, but no sibling in the catalog overlaps with supplier discovery, so an agent can still identify it unambiguously.

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 gives clear procedural guidance for the paid flow: 'call without x402_payment to get the payment requirements' and the per-call price, plus the optional sector/country filters. What is missing is any when-not guidance or explicit alternative (e.g. when to prefer a basic lookup instead), so it stops short of full routing guidance.

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