Skip to main content
Glama

MyProduct: Find AI Mapping Candidates

search_ai_mapping_candidates
Read-onlyIdempotent

[Store Products] [What it does] Finds visually similar supplier item for one DSers product via image search, with price, stock, freight, rating, and similarity evidence; creates or applies no mapping. [When to use] Use when the merchant wants to compare suppliers before mapping a managed product. [When not to use] For a general supplier-catalog search, use search_supplier_products; to start the selected mapping computation, use start_ai_product_mapping. [How to use] Copy dsers_product_id from list_managed_store_products; ship_to sets destination context for availability and freight. Zero matches is a valid result and may include a reason; missing price, rating, or similarity remain unknown. [Side effects] Read-only; neither creates nor applies a mapping. [Confirmation] No confirmation required. [Follow-up] If the merchant selects a suitable candidate, start its computation with start_ai_product_mapping; if none fits, report the result and stop.

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": {
      "dsers_product_id": "<dsers_product_id>"
    },
    "name": "search_ai_mapping_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoWhen true, ask Product BFF to refresh picture-search candidates instead of using its cache.
ship_toNoDestination country code used for supplier availability and freight; defaults to US.US
dsers_product_idYesCopy from items[].dsers_product_id in list_managed_store_products results. Required.

Output Schema

NameRequiredDescriptionDefault
ship_toYesDestination country used for supplier and freight lookup
refreshedYesWhether Product BFF was asked to bypass its picture-search cache
candidatesYesAI Mapping supplier candidates in upstream recommendation order
next_actionsYesOptional follow-up tools; no mapping is created by this search
matched_countYesNumber of candidates returned
dsers_product_idYesSource DSers My Product ID as a decimal string
no_result_reasonNoExplanation when no candidates are available
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, and the description goes further with behavior an agent cannot infer: zero matches is a valid result (sometimes with a reason), and missing price/rating/similarity stay unknown rather than being errors. It also states no confirmation is required, which prevents an unnecessary confirmation loop.

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?

The bracketed section headers make the definition scannable and front-load purpose before guidance. There is minor redundancy: the "creates or applies no mapping" claim appears both in [What it does] and again under [Side effects].

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?

For a three-parameter read tool with an output schema, everything an agent needs to call it correctly is present: purpose, prerequisites for the ID, destination context, empty-result semantics, and the next step. Return-value details are correctly left to the output schema.

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?

Schema coverage is 100%, so provenance and semantics of dsers_product_id, ship_to, and refresh are already documented in the schema. The description only restates that dsers_product_id is copied from list_managed_store_products and that ship_to sets destination context, and never mentions refresh's cache-bypass behavior — so it adds little beyond the schema, matching the baseline 3.

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?

"Finds visually similar supplier item for one DSers product via image search" names a specific verb, resource, and mechanism, plus the evidence returned (price, stock, freight, rating, similarity). It explicitly distinguishes itself from lookup/mapping siblings by stating it creates or applies no mapping.

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?

The [When to use] block gives the merchant intent (compare suppliers before mapping a managed product), and [When not to use] names two concrete alternatives with the condition that selects each: search_supplier_products for general catalog search, start_ai_product_mapping to start computation. The [Follow-up] block completes the routing.

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.