Skip to main content
Glama

Get a Telegram gift

get_gift
Read-onlyIdempotent

Use this to look up one numbered upgraded Telegram gift, for example Plush Pepe #9998: traits (model, backdrop, symbol), rarity, the published price estimate in Stars, TON and USD, recent sales and the active listing. Give collection and number, or a slug such as "plushpepe-9998". Do not use it for a whole collection (get_collection), to find the cheapest places to buy (where_to_buy) or to find who owns a gift (not available).

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

Input Schema

NameRequiredDescriptionDefault
slugNoGift slug or t.me/nft link, for example "plushpepe-9998".
numberNoThe gift number inside the collection.
collectionNoCollection name, for example "Plush Pepe".

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
modelYes
priceNo
numberYes
symbolNo
backdropYes
image_urlNo
valuationNo
collectionYes
last_salesNo
telegram_urlNo
active_listingNo
model_rarity_percentNo
backdrop_rarity_percentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/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 openWorldHint=false, so safety is covered by structured data; the description's added value is behavioral scope — it reports that price figures are published estimates, that recent sales and an active listing are included, and that owner lookup is not supported. It does not mention rate limits, caching or staleness of estimates, which would push it higher.

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?

Three sentences, front-loaded with the core action and payload, then input forms, then exclusions. Every clause carries information; nothing is redundant with the title or schema.

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?

With a rich annotation set and an output schema, the description only needed to cover selection guidance, input forms and scope limits — and it does all three. Nothing an agent needs to call this 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, but the description adds real meaning by spelling out the two alternative input modes — collection+number versus a single slug like "plushpepe-9998" — which clarifies the relationship between the three optional parameters (all optional, so an agent needs this routing guidance). It stops short of stating precedence when both forms are supplied.

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 (look up one numbered gift), enumerates the returned content (traits, rarity, price estimates in Stars/TON/USD, recent sales, active listing), and explicitly names the siblings it is not (get_collection, where_to_buy). An agent can distinguish it from all listed siblings 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?

Gives explicit when-to-use (one numbered gift, e.g. Plush Pepe #9998) and explicit when-not-to-use with named alternatives for each exclusion case: get_collection for whole collections, where_to_buy for cheapest purchase venues, and a stated non-available case for ownership lookup.

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