Skip to main content
Glama

List the shop

shop_packs
Read-onlyIdempotent

The whole shop, as a human player's shop screen shows it: the packs (sku, name, USD price, what each gives, and once logged in whether this account can buy it now and by which real-money methods: stripe = a card through a Stripe shared payment token, tempo = USDC on Tempo, x402 = USDC on Base), the limited-time sales on right now (buy with sale_id), the diamond shop (items bought with the game command shop.buy {sku} through send_command), and this account's store credit. Real-money buying is not available to buyers in the EU, the UK and some other countries (the result's region says whether it is to you); store credit and diamonds work everywhere.

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

Input Schema

NameRequiredDescriptionDefault
tokenNothe token your login returned; pass it when a call answered not_logged_in after you logged in

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties
      Added value: +{
      +  "token": {
      +    "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.4/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent profile, but the description adds substantial behavioral context: results vary by login state, purchase eligibility is per-account, and real-money buying is unavailable in the EU, the UK and other countries while store credit and diamonds work everywhere. It also decodes the payment-method values (stripe = card via Stripe shared token, tempo = USDC on Tempo, x402 = USDC on Base), which annotations cannot convey.

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 whole shop' and every clause carries information an agent needs (returned sections, payment methods, region limits). It is a single long sentence with heavily nested parentheticals, which slightly hurts scanability but not waste.

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?

Despite an output schema existing, the description explains the shape of the result (packs, sales with sale_id, diamond items, store credit) plus region gating and payment methods. For a one-optional-param read tool this leaves nothing an agent needs in order to call it and interpret the response correctly.

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% and the single optional `token` parameter is already well documented there. The description only alludes to login state ('once logged in') without explaining the token parameter itself, so it adds little beyond the schema — the baseline 3 is appropriate.

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 ('The whole shop... the packs ..., the limited-time sales ..., the diamond shop ..., and this account's store credit'), enumerating exactly what the response contains. It is clearly distinguishable from siblings like buy_pack, buy_pack_with_store_credit and send_command, which it even name-checks as the purchase path.

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?

Implies the discovery-then-buy flow by saying sales are bought 'with sale_id' and diamond items 'through send_command', steering the agent to the correct follow-up tools. It does not explicitly say 'call this before buy_pack' or state any exclusions, so it falls short of full when/when-not guidance.

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