Worth

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

Name	Required	Description	Default
`place`	No	Kind of shop nearby, such as card shop.
`title`	Yes	Item name.
`intent`	No	What the user wants to do.	any
`category`	No	Category hint.

Output Schema

Name	Required	Description	Default
`best`	Yes
`name`	Yes
`view`	Yes
`comps`	No
`links`	Yes
`priced`	Yes
`outcome`	Yes
`currency`	Yes
`headline`	Yes
`new_from`	Yes
`from_past`	No
`new_label`	Yes
`retailers`	No
`used_from`	Yes
`confidence`	Yes
`resale_low`	Yes
`used_label`	Yes
`resale_high`	Yes
`estimate_low`	Yes
`resale_label`	Yes
`estimate_high`	Yes
`confidence_label`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026
- addedOutput schema / properties / from_past
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / retailers
```
Added value: +{
+  "type": "array"
+}
```
Changed2 schema fields changedOct 21, 2026
- addedOutput schema / properties / comps
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / confidence_label
```
Added value: +{
+  "type": "string"
+}
```
First observedOct 21, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish safety as read-only, open-world, idempotent, and non-destructive. The description adds useful behavioral context: it returns only URLs, and those links are Worth tracking links that may carry affiliate tags.

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 three tight sentences with no waste. Purpose is front-loaded, followed by return scope and affiliate disclosure.

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?

For a simple read-only link lookup with an output schema, full parameter coverage, and annotations, the description covers the important caveats. It could be slightly stronger if it explicitly positioned the tool against its price-focused siblings.

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 the parameters are already well documented. The description paraphrases the intent options but adds no meaningful semantics for place or category beyond what the schema provides.

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 and resource: returns marketplace links to buy one named item new, buy it used, or sell it. It is clear about the output being links, but it does not explicitly distinguish this from sibling tools like compare_prices or price_item.

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 use case is implied by the buy/sell wording, and the description narrows output to marketplace URLs. However, it gives no explicit when-to-use guidance relative to compare_prices or price_item, and no exclusions.

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

All Worth tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.