Skip to main content
Glama

Recent gift sales

recent_sales
Read-onlyIdempotent

Use this for the latest completed sales of a collection or one model in the last 90 days, with price in TON, Stars and USD, the marketplace and the date. Do not use it for current asking prices (where_to_buy), for the price estimate (get_collection, get_model) or for the sales of one numbered gift (get_gift).

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": {
      "collection": "<collection>"
    },
    "name": "recent_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows, default 10.
modelNoOptional model name.
collectionYesCollection name in English or Russian, for example "Plush Pepe".

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
modelNo
salesYes
collectionYes
window_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add what annotations cannot express. It does add meaningful context: only completed sales within a fixed 90-day window, and prices normalized into three currencies with marketplace and date. It doesn't clarify how the default limit or ordering behaves beyond what the schema states.

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?

Two sentences, both dense with information, with the positive use case front-loaded and the exclusions following. No redundant restatement of the title or name.

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, so return values needn't be spelled out, and the description still previews the key fields and currencies. For a low-complexity read tool with full schema coverage and clear annotations, nothing an agent needs to select or call it correctly is missing.

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 schema already documents all three parameters, including the collection name format and the limit range. The description adds marginal meaning by framing 'model' as narrowing the query to a single model of a collection, but contributes nothing on limit behavior or how model interacts with collection.

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?

The description names a specific verb+resource (latest completed sales) and pins down the scope: a collection or a single model, within the last 90 days. It also states what each row contains (price in TON, Stars, USD, marketplace, date), so the agent can distinguish it from price-estimate and asking-price tools without reading any 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?

It gives explicit routing instructions for the three nearest alternatives: where_to_buy for current asking prices, get_collection/get_model for price estimates, and get_gift for a single numbered gift's sales. The negative cases are named with their tools, leaving nothing to inference.

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