Skip to main content
Glama

Where to buy a gift

where_to_buy
Read-onlyIdempotent

Use this when the user wants to buy: the cheapest stored active listings of a collection, model, backdrop or one numbered gift, each with marketplace, price in Stars, TON and USD and the link that opens it, plus the stored Portals ask floor. It reads stored listings, not a live marketplace, and never places an order. Do not use it for what a gift is worth (get_gift) or for past sales (recent_sales).

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": "where_to_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoGift slug such as "plushpepe-9998", to look up one gift.
limitNoListings, default 5.
modelNoOptional model name.
numberNoGift number, to look up one gift.
backdropNoOptional backdrop name.
collectionNoCollection name in English or Russian, for example "Plush Pepe".

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
modelNo
messageNo
backdropNo
listingsYes
collectionYes
other_marketplacesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope, so the safety profile is covered. The description still adds genuinely new behavioral context: the data is stored listings rather than a live marketplace, and it never places an order — a freshness caveat an agent could not derive from structured fields. Minor gaps remain around result counts pagination beyond the limit parameter.

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?

Two sentences, front-loaded with the trigger and the payload description, followed by the boundaries. The first sentence is dense and heavily comma-laden but every clause carries real information; no filler or restated title.

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?

An output schema exists, yet the description still summarizes the return shape, and it covers data provenance, non-mutation, and sibling routing. For a six-parameter, zero-required read tool, nothing an agent needs to select or invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description goes beyond it by clarifying the two lookup modes — a whole collection/model/backdrop versus 'one numbered gift' — which explains how slug/number interact with collection/model/backdrop in a way the schema fields alone leave implicit.

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?

States a concrete verb and resource — returning the cheapest stored active listings for a collection, model, backdrop, or single numbered gift — and enumerates what each result carries (marketplace, price in Stars/TON/USD, opening link, Portals ask floor). This is distinguishable from every sibling without opening the schema.

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?

Opens with an explicit trigger ('Use this when the user wants to buy') and closes with explicit exclusions routed to named alternatives: get_gift for valuation and recent_sales for past sales. Both the when and the when-not are stated, not inferred.

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