Skip to main content
Glama

Gift a pack (real money)

gift_pack
Destructive

Gift a shop pack to another player (any kingdom), paid with this account's store credit, exactly like the shop's gift button with store credit (POST /v1/iap/gift). Find the player with find_players. To pay with real money instead, use buy_pack with gift_to_account_id. The recipient is told at once, with your message, and the pack arrives 3 days after it was paid for (arrives_at_ms; a refund before then cancels it); big gifts are announced in world chat when they arrive. A gift is the pack at its listed price, with a daily cap.

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

Input Schema

NameRequiredDescriptionDefault
skuYesthe pack's sku, from shop_packs
tokenNothe token your login returned; pass it when a call answered not_logged_in after you logged in
messageNooptional message shown with the gift (max 200 characters)
to_account_idNothe recipient's account_id, from find_players (preferred: names can repeat)
to_display_nameNoor the recipient's exact display name

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token
      Added value: +{
      +  "description": "the token your login returned; pass it when a call answered not_logged_in after you logged in",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the bar is lower. The description still adds real value beyond them: recipient is notified immediately with the message, delivery is delayed 3 days after payment (arrives_at_ms), a refund before then cancels the gift, large gifts are announced in world chat, the price is the listed price, and a daily cap applies.

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 purpose, payment source and endpoint, then delivery semantics, then the alternative tool. It is a single dense paragraph; the parenthetical endpoint and arrives_at_ms field name are useful but push it toward maximum density rather than optimal brevity.

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?

An output schema exists, so return values need not be explained. What an agent still needs to call this safely — payment source, recipient discovery, delivery delay, cancellation window, daily cap, social side effects — is all present.

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%, so sku, token, message, to_account_id and to_display_name are already documented, including the preference for account_id over display name. The description's only real addition is the cross-reference to find_players and shop_packs as sources for those values, which is marginal beyond the schema.

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?

Names a specific verb and resource (gift a shop pack to another player), states the payment source (this account's store credit), the scope (any kingdom), and even the underlying endpoint (POST /v1/iap/gift). It is immediately distinguishable from buy_pack (real money) and gift_code_pack without opening any 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 routes the agent: use find_players to locate the recipient, and use buy_pack with gift_to_account_id when paying with real money instead of store credit. Both the preferred path and the alternative are named with the condition that selects them.

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