Skip to main content
Glama

Get a gift symbol

get_symbol
Read-onlyIdempotent

Use this for a gift symbol (the pattern on a gift, for example "Ruby") and its rarity, in one collection or across all. If symbol data is not stored yet the result says available=false; do not guess a rarity. Do not use it for models or backdrops.

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

Input Schema

NameRequiredDescriptionDefault
nameNoSymbol name. Leave empty to list the symbols of a collection.
collectionNoOptional collection name.

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
statusYes
symbolNo
messageNo
symbolsYes
availableYes
collectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral context: a result can come back with available=false when the symbol isn't stored, and the agent must not fabricate a rarity in that case. That failure-mode guidance is the kind of thing annotations cannot express. It does not discuss pagination or the shape of the rarity value, minor gaps given an output schema exists.

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 short sentences, zero padding: purpose and scope first, then the unavailable-data fallback, then the exclusion. Each sentence earns its place and the most important constraint is front-loaded.

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?

With an output schema present, the return shape need not be restated, and the description covers the one behavioral wrinkle an agent could get wrong (the available=false case). Zero required parameters and a fully documented schema mean little else is needed; only the omission of an explicit alternative for the excluded resource types keeps it from a 5.

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 both parameters are already documented in the schema, so the baseline is 3. The description does add a little meaning by clarifying that the scope can be a single collection or all of them, which frames how `collection` interacts with `name`, but it does not restate the "leave empty to list" behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely and even defines the domain term ("a gift symbol (the pattern on a gift, for example \"Ruby\") and its rarity"), plus the scope (one collection or across all). It only lacks an explicit retrieval verb, so it reads as a statement of subject matter rather than a crisp action, but an agent can still tell what it returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit negative boundary — "Do not use it for models or backdrops" — which routes the agent toward get_model/get_backdrop. It also warns not to guess a rarity when available=false. It stops short of naming the sibling to use instead for gifts or collections, so the alternatives are implied rather than spelled out.

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