MCP Affiliate Server

Overview Schema Source Related Servers Discussions Admin

match_bom

Match a Bill of Materials against affiliate product catalogs to get best matches with prices and affiliate links for each component.

Instructions

Match a Bill of Materials (list of components/parts) against affiliate product catalogs. Returns best matches with prices and affiliate links for each item. Ideal for project material lists.

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": {
      "items": "<items>"
    },
    "name": "match_bom"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	List of BOM items (e.g., ["6x STS3215 Servo", "1x ESP32 DevKit", "PLA Filament 1kg"])
`networks`	No	Limit search to specific networks. Default: all configured networks.
`marketplace`	No	Target marketplace. Default: "de".	de
`max_shops_per_item`	No	Max shop links per BOM item (1-5). Default: 3.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the primary behavior (returns best matches with prices and affiliate links) but lacks details on edge cases like no matches found, partial matching, or any side effects. This is adequate but not deeply transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences fully convey the tool's purpose and output with zero filler. The structure is front-loaded with the action and resource, making it efficient for an agent to parse.

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?

Despite lacking an output schema, the description provides a high-level summary of the return format (best matches, prices, affiliate links). It covers the essential context for a matching tool, though it could detail what 'best match' means or how multiple networks are handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers 100% of parameter descriptions, so the baseline is 3. The description adds marginal value by reinforcing that items are a list of components/parts and that output includes prices and links, but it does not clarify network or marketplace specifics beyond the schema.

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 clearly states the tool's function: matching a Bill of Materials against affiliate product catalogs and returning best matches with prices and links. The verb 'Match' and resource 'Bill of Materials' distinguish it from sibling tools like search_products, which likely handles single product queries.

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 phrase 'Ideal for project material lists' provides clear context for when to use this tool. It implies multi-item input scenarios but does not explicitly mention when not to use it or alternatives, which would earn a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server