Skip to main content
Glama

Get a gift collection

get_collection
Read-onlyIdempotent

Use this for a Telegram gift collection such as "Plush Pepe": lowest published price estimate in Stars, TON and USD, supply, the 24h and 7d change of its lowest ask (there is no longer price history), and its models with their price estimates and rarity. Do not use it for market-wide rankings (top_collections) or for current listings (where_to_buy).

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

Input Schema

NameRequiredDescriptionDefault
nameYesCollection name in English or Russian, for example "Plush Pepe".

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
priceNo
modelsYes
supplyNo
image_urlNo
collectionYes
floor_starsNo
model_countNo
change_basisNo
backdrop_countNo
change_7d_percentNoPercent change of the lowest ask over 7 days, from the stored floor change log; null when there was no ask then. See change_basis / caveat.
change_24h_percentNoPercent change of the lowest ask over 24 hours, from the stored floor change log; null when there was no ask then. See change_basis / caveat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the description needn't restate safety. It adds real behavioral context beyond them: the 'there is no longer price history' caveat warns the agent not to expect historical series, and it enumerates the returned metrics. It does not say what happens for an unknown or misspelled collection name, which keeps it from 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?

Front-loaded with the use case, then the return payload, then the exclusions — a logical order with no filler. The return-field enumeration is somewhat long and partly duplicates the output schema, which costs it a point.

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?

A one-parameter read tool with full annotations and an output schema; the description covers purpose, routing, and the important no-history caveat. Since an output schema exists, the field-by-field return list is redundant rather than necessary, and error behavior for invalid names remains unaddressed.

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 coverage is 100% and the single parameter already documents that the name may be English or Russian with a "Plush Pepe" example. The description repeats that example but adds no further naming rules (aliases, casing, partial matches), so the baseline 3 for fully covered schemas applies.

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 specific verb and resource (get a Telegram gift collection) and enumerates exactly what is returned: lowest published price estimate in Stars/TON/USD, supply, 24h and 7d change of lowest ask, and models with price estimates and rarity. It names the sibling tools it is not (top_collections, where_to_buy), so an agent can discriminate it without opening another 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?

Explicitly gives both sides of the routing decision: use this for a single named collection, do not use it for market-wide rankings (top_collections) or current listings (where_to_buy). The example name "Plush Pepe" anchors the expected input granularity.

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