Skip to main content
Glama

Get a gift backdrop

get_backdrop
Read-onlyIdempotent

Use this for a backdrop colour such as "Black": rarity and observed prices. With a collection it gives that collection's backdrop; without one it lists every collection where the backdrop appears. Do not use it for models or symbols. The Telegram ask is a TON price (telegram_ask_ton); telegram_ask_stars is that ask at the display rate, approximate.

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_backdrop"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesBackdrop name, for example "Black".
collectionNoOptional collection name.

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
backdropYes
collectionNo
collectionsNo
models_seenNo
rarity_percentNo
telegram_ask_tonNo
telegram_ask_starsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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 the safety profile is covered. The description adds the genuinely non-obvious behavior: the result shape changes drastically depending on whether `collection` is supplied (single row vs. all-collection listing). The note that telegram_ask_stars is an approximate conversion of telegram_ask_ton adds useful interpretation context for the returned values, though it is arguably output-schema territory.

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?

Three tight sentences, front-loaded with the core purpose and mode switch, and the exclusion follows immediately. The opening clause ("Use this for a backdrop colour such as \"Black\": rarity and observed prices") reads slightly awkwardly, but nothing is redundant.

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 tool with full schema coverage and an output schema, this covers everything an agent needs: purpose, mode-dependent behavior, sibling exclusion, and a caveat on the approximate price field. No material gap remains.

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 would be 3, but the description adds real meaning beyond the schema's bare "Optional collection name" by explaining that its presence switches between collection-scoped lookup and a global listing. That is the key semantic an agent needs and it is not derivable from the schema alone.

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 resource (a gift backdrop colour such as "Black") and states what is returned: rarity and observed prices. It also explicitly carves itself away from siblings by saying it is not for models or symbols, so an agent can pick it over get_model/get_symbol without inspecting schemas.

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 the two operating modes and the condition that selects each: with a collection you get that collection's backdrop, without one you get every collection where the backdrop appears. It also states a clear negative case ("Do not use it for models or symbols"), which points the agent at the right sibling family.

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