Skip to main content
Glama

Top gift collections

top_collections
Read-onlyIdempotent

Use this for the market overview: which collections trade most, have the lowest or highest ask, or the most listings, with the lowest ask in Stars, TON and USD, the number of Telegram listings and MRKT plus Portals sales and TON volume in the last 24 hours, plus the 24h and 7d change of the lowest ask (from the stored floor change log; null when a collection had no ask then). Do not use it for one named collection (get_collection).

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

Input Schema

NameRequiredDescriptionDefault
sortNoRanking, default sales_24h.
limitNoRows, default 10.

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
sortYes
caveatNo
windowNo
collectionsYes
change_availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for the extra behavioral detail it adds: the 24h measurement window, the fact that floor change comes from a stored change log, and that it is null when a collection had no ask at that time. It doesn't discuss limits or freshness beyond that, which keeps it short of a 5.

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?

The usage instruction and the exclusion are front-loaded in the first and last clauses, and every clause carries information rather than restating the name. It is, however, one dense run-on sentence with a long comma-separated metric list, which is harder to scan than a short bulleted structure.

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 don't need explaining, yet the description still tells the agent what fields to expect and how nulls arise. Combined with the sibling exclusion and the 24h window, an agent has everything needed to select and call this tool correctly.

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% and both parameters carry their own description and defaults, so the schema does the heavy lifting. The prose implicitly maps its ranking phrasings ('trade most', 'lowest or highest ask', 'most listings') to the sort enum values, but never names the sort or limit parameters, so the extra meaning is inferential rather than stated.

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 pair ('market overview' of collections) and enumerates the exact dimensions it ranks on: trading volume, lowest/highest ask, listing counts, and 24h/7d floor change. It also explicitly excludes the single-collection case by naming the sibling get_collection, so an agent can separate it from the other collection tool without opening a 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 an explicit when-to-use ('Use this for the market overview') and an explicit when-not-to-use with the correct alternative ('Do not use it for one named collection (get_collection)'). That is a complete routing rule, not an implied one.

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