Skip to main content
Glama

Where to buy or sell

where_to_buy_or_sell
Read-onlyIdempotent

Marketplace links to buy one named item new, buy it used, or sell it. Returns marketplace links for the item; these are the only URLs this tool provides. Links are Worth tracking links and may carry affiliate tags.

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": {
      "title": "<title>"
    },
    "name": "where_to_buy_or_sell"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoKind of shop nearby, such as card shop.
titleYesItem name.
intentNoWhat the user wants to do.any
countryNoISO 3166-1 alpha-2 code of the country the user is in when it is outside the US, such as SE, DE, or GB. Listings come from that country's marketplaces and prices are in its currency. Empty for the US or when unknown.
categoryNoCategory hint.
currencyNoISO 4217 code of the currency the user prices in when it is not USD, such as EUR, SEK, or GBP. Empty to follow country, or USD.

Output Schema

NameRequiredDescriptionDefault
bestYes
nameYes
viewYes
compsNo
linksYes
pricedYes
outcomeYes
currencyYes
headlineYes
new_fromYes
from_pastNo
new_labelYes
retailersNo
used_fromYes
confidenceYes
resale_lowYes
used_labelYes
resale_highYes
estimate_lowYes
resale_labelYes
estimate_highYes
confidence_labelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "default": "",
      +  "description": "ISO 3166-1 alpha-2 code of the country the user is in when it is outside the US, such as SE, DE, or GB. Listings come from that country's marketplaces and prices are in its currency. Empty for the US or when unknown.",
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • addedInput schema / properties / currency
      Added value: +{
      +  "default": "",
      +  "description": "ISO 4217 code of the currency the user prices in when it is not USD, such as EUR, SEK, or GBP. Empty to follow country, or USD.",
      +  "maxLength": 40,
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / from_past
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / retailers
      Added value: +{
      +  "type": "array"
      +}
  3. Changed2 schema fields changed
    • addedOutput schema / properties / comps
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / confidence_label
      Added value: +{
      +  "type": "string"
      +}
  4. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety bar is low. The description still adds non-obvious context: results are Worth tracking links that may carry affiliate tags, and links — not prices — are the entire payload. That affiliate disclosure is exactly the kind of trust-relevant behavior structured fields cannot convey.

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 short sentences, front-loaded with what the tool returns. 'Returns marketplace links for the item' slightly restates the opening sentence, but the later clauses about URL exclusivity and affiliate tags each earn their place.

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?

An output schema exists, so return-value structure need not be explained, and annotations cover the safety profile. The description supplements this with the affiliate-tag caveat and the 'links only, no prices' boundary, which is what an agent most needs to route correctly. Only the missing sibling routing guidance keeps it from a 5.

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 description coverage is 100%, so country, currency, place, and category are already well documented with examples and defaults. The description echoes the intent modes (new, used, sell) and the single-item constraint but adds no format or edge-case detail beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 a specific verb and resource: returns marketplace links to buy a named item new, buy it used, or sell it. That distinguishes it implicitly from price-oriented siblings like compare_prices and price_item, since it explicitly says these are the only URLs it provides. It never names a sibling, so differentiation is inferred rather than stated.

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?

There is no statement of when to choose this over compare_prices or price_item, nor any precondition or exclusion. The scope phrase 'one named item' hints at the intended call shape but is not usage guidance. An agent must infer the routing decision from tool names alone.

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