Skip to main content
Glama

Pet Welcome Box – hand-picked gift ideas

Resolve buy link

resolve_product
Read-only

Resolve ASIN, Amazon URL, or keywords to a buyUrl on the chosen storefront. amazon.com links carry sw-petbox-20, amazon.se links sw-petbox-21 (trackingTag). marketplace optional (fallback: country → en-US → amazon.com → else amazon.se).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resolve_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
asinNo
stageNo
localeNoUser locale, e.g. en-US (US shoppers → amazon.com) or sv-SE (Sweden → amazon.se). If marketplace and country are omitted, en-US selects amazon.com.
countryNoISO country of the shopper, used when marketplace is omitted: US → amazon.com, SE → amazon.se.
speciesNo
keywordsNo
sizeBandNo
budgetBandNo
kitCategoryNo
marketplaceNoAmazon storefront: amazon.com (United States — 224 hand-picked products, English, USD, /dp/ links tagged sw-petbox-20) or amazon.se (Sweden, default — 440 products, tag sw-petbox-21); ids us / se also work. Optional: when omitted → country, then locale / Accept-Language en-US → amazon.com, otherwise amazon.se. Other storefronts get search links.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "ISO country of the shopper, used when marketplace is omitted: US → amazon.com, SE → amazon.se.",
      +  "maxLength": 3,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • changedInput schema / properties / locale / description
      Previous value: -"User locale, e.g. en, sv, de, fr, es"New value: +"User locale, e.g. en-US (US shoppers → amazon.com) or sv-SE (Sweden → amazon.se). If marketplace and country are omitted, en-US selects amazon.com."
    • changedInput schema / properties / marketplace / description
      Previous value: -"Amazon storefront domain or id, e.g. amazon.com, amazon.se, us, se. REQUIRED."New value: +"Amazon storefront: amazon.com (United States — 224 hand-picked products, English, USD, /dp/ links tagged sw-petbox-20) or amazon.se (Sweden, default — 440 products, tag sw-petbox-21); ids us / se also work. Optional: when omitted → country, then locale / Accept-Language en-US → amazon.com, otherwise amazon.se. Other storefronts get search links."
    • removedInput schema / required
      Removed value: -[
      -  "marketplace",
      -  "locale"
      -]
  2. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, and the description adds useful behavioral context: generated links carry tracking tags (sw-petbox-20 or sw-petbox-21) depending on storefront, and marketplace selection follows a documented fallback chain. It does not cover error behavior or return details beyond buyUrl, but the added tracking-tag disclosure is valuable.

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?

The description is two tightly written sentences with the core purpose front-loaded, followed by storefront and tracking-tag details. There is no filler, and the fallback chain is compactly expressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter, zero-required tool with no output schema, the description is not complete enough. It covers the main resolution modes and marketplace fallback, but omits the roles of several optional filtering parameters and does not explain how the input modes interact.

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

Parameters2/5

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

Schema coverage is only 27%, and the description compensates for just some parameters: url, asin, keywords, marketplace, country, and locale are partially addressed. It leaves stage, species, sizeBand, budgetBand, and kitCategory unexplained, and does not clarify precedence among url, asin, and keywords.

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 states a specific verb+resource: resolve an ASIN, Amazon URL, or keywords to a buyUrl on a chosen storefront. This is clearly distinct in substance from sibling tools like search or add_item, though it does not explicitly name those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains storefront fallback behavior but gives no explicit guidance on when to use this tool instead of search or list_marketplaces. Usage is only implied by the resolve-to-buyUrl purpose.

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