Skip to main content
Glama

Get a gift model

get_model
Read-onlyIdempotent

Use this for one model of a collection (for example Plush Pepe / Heart): rarity, lowest estimate in Stars, TON and USD, price estimate by backdrop and observed asks and sale floors. The Telegram ask is a TON price (telegram_ask_ton); telegram_ask_stars is that ask at the display rate, approximate. Do not use it for 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>",
      "model": "<model>"
    },
    "name": "get_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel name inside the collection, for example "Heart".
collectionYesCollection name in English or Russian, for example "Plush Pepe".

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
modelYes
priceNo
image_urlNo
collectionYes
by_backdropYes
floor_starsNo
rarity_percentNo
portals_ask_tonNo
priced_backdropsNo
telegram_ask_tonNo
telegram_ask_starsNo
recent_sales_pricedNo
recent_sales_floor_tonNo

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 declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: telegram_ask_ton is the native TON ask while telegram_ask_stars is that ask converted at the display rate and therefore approximate — a data-reliability caveat the schema cannot express. It stops short of describing ordering or whether estimates are live versus cached.

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 purpose in the first clause, then the exclusion last, so the most decision-relevant information is early. The middle sentence is dense with field names and currency jargon but each part carries real information about the returned values, so little is wasted.

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?

For a two-parameter, read-only lookup with full schema coverage, complete annotations, and an output schema, the description covers purpose, scope routing, and the one qualitative data caveat that matters. Nothing an agent needs in order to 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 both parameters are already documented, making 3 the baseline. The description's inline examples ("Plush Pepe / Heart") largely restate the schema's own examples and add no new syntax, constraints, or format rules beyond what the schema provides.

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: "one model of a collection" with concrete examples (Plush Pepe / Heart) and enumerates what it returns (rarity, lowest estimate in Stars/TON/USD, price estimate by backdrop, observed asks and sale floors). It also explicitly distinguishes itself from get_gift, so an agent can route without opening either 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 a positive usage condition ("Use this for one model of a collection") and an explicit exclusion with the alternative named ("Do not use it for one numbered gift (get_gift)"). The scope boundary between the model-level and gift-level tools is unambiguous, which is exactly the failure mode an agent would otherwise hit.

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