Skip to main content
Glama

Dorm Kit – hand-picked gift ideas

Resolve product buy link

resolve_product

Resolve ASIN, Amazon URL, or keywords to a buy deep-link on the selected marketplace. amazon.se links carry ?tag=sw-dormkit-21; amazon.com links carry ?tag=sw-dormkit-20. Missing store falls back (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
localeNoBCP-47 locale for the shopper (e.g. en-US, sv-SE). Recommended; en-US without a marketplace selects amazon.com.
categoryNo
keywordsNo
budgetBandNo
marketplaceNoAmazon storefront id (us, se) or domain (amazon.com, amazon.se). Recommended. For US shoppers pass marketplace=amazon.com (US catalog, amazon.com /dp/ links, tag sw-dormkit-20). If omitted: locale en-US selects amazon.com, anything else falls back to amazon.se (never an error).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / locale / description
      Previous value: -"BCP-47 locale for the shopper (e.g. en-US, sv-SE). REQUIRED."New value: +"BCP-47 locale for the shopper (e.g. en-US, sv-SE). Recommended; en-US without a marketplace selects amazon.com."
    • removedInput schema / properties / locale / minLength
      Removed value: -1
    • changedInput schema / properties / marketplace / description
      Previous value: -"Amazon marketplace id (e.g. us, se) or domain (e.g. amazon.com, amazon.se). REQUIRED."New value: +"Amazon storefront id (us, se) or domain (amazon.com, amazon.se). Recommended. For US shoppers pass marketplace=amazon.com (US catalog, amazon.com /dp/ links, tag sw-dormkit-20). If omitted: locale en-US selects amazon.com, anything else falls back to amazon.se (never an error)."
    • removedInput schema / properties / marketplace / minLength
      Removed value: -1
    • removedInput schema / required
      Removed value: -[
      -  "marketplace",
      -  "locale"
      -]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the affiliate tag appended per marketplace and the never-error fallback chain, which are real behavioral traits. It says nothing about what happens when an ASIN/keyword cannot be resolved, or that the tool performs no writes.

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?

Three dense sentences, front-loaded with the core conversion and followed by the tag and fallback details an agent needs before choosing a marketplace. Minor parenthetical clutter, but no wasted text.

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?

Given zero required parameters, the most important missing piece is that at least one of asin/url/keywords must be supplied, which is never stated. Beyond that, the marketplace selection logic—the trickiest part of calling this correctly—is fully documented, and no output schema exists to explain.

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 only 29%, so the description must compensate. It does explain marketplace/locale behavior and the tag suffix per store, and it names asin/url/keywords as the input forms, but category and budgetBand are left completely undefined in both schema and description, and no input precedence is given when several are supplied.

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?

Names a specific verb (resolve) and the exact transformation: ASIN/URL/keywords into a marketplace buy deep-link. The resource and direction of conversion are unambiguous, and no sibling tool (all kit/catalog operations) could be confused with it, though the description never explicitly contrasts them.

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

Usage Guidelines3/5

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

The fallback sentence ('Missing store falls back…') implies what to do when marketplace is absent, but there is no explicit 'use this when' statement, no guidance on which input form to prefer (ASIN vs URL vs keywords), and no mention of what to do if resolution fails.

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