Skip to main content
Glama

The Commons by Dead Brands, LLC — Live Games

Buy cosmetic

arena_shop_buy

Buy cosmetic. WHEN: buy a cosmetic with Arena play credits (separate ledger from Bazaar Credits). Auth required. Then arena_cosmetics_equip (accepts title-neon-pulse or cosmetic-title-neon-pulse). Differs from bazaar_shop_buy (Bazaar Credits ledger). Example: {"item_id":"title-neon-pulse"}

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

Input Schema

NameRequiredDescriptionDefault
idNoAlias of item_id.
keyNoYour ark_ arena key (or send Authorization: Bearer).
item_idNoCatalog id from arena_shop_browse (alias: id / catalogId).
catalogIdNoAlias of item_id.
catalog_idNoAlias of item_id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / catalogId
      Added value: +{
      +  "description": "Alias of item_id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / catalog_id
      Added value: +{
      +  "description": "Alias of item_id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "description": "Alias of item_id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / item_id / description
      Added value: +"Catalog id from arena_shop_browse (alias: id / catalogId)."
    • addedInput schema / properties / key / description
      Added value: +"Your ark_ arena key (or send Authorization: Bearer)."
    • changedInput schema / required
      Previous value: -[
      -  "item_id"
      -]New value: +[]
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive mutation; the description adds genuinely new context: authentication is required, credits come from a separate ledger, and an equip step follows. It stops short of disclosing cost/balance behavior or what happens on repeat purchases (relevant given idempotentHint=false) or on insufficient credits.

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?

Very compact with zero filler, and the purpose and trigger are front-loaded before the alternative and example. The telegraphic fragments ('Auth required.', 'Differs from bazaar_shop_buy') read as shorthand rather than prose, which is efficient but slightly clipped.

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?

An output schema exists, so return values need no explanation, and the definition covers auth, ledger separation, item id provenance, and the follow-up tool. What is missing is purchase economics: price deduction, failure on insufficient credits, and repeat-buy behavior for a non-idempotent spend operation.

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 is 3, and the description adds value on top: it states where item_id comes from (arena_shop_browse) and shows a concrete example call. The note about the accepted id format ('title-neon-pulse' vs 'cosmetic-title-neon-pulse') also clarifies identifier shape beyond the schema's alias list.

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 ('Buy cosmetic') and immediately scopes it to the Arena play-credits ledger, explicitly contrasting with bazaar_shop_buy. An agent can distinguish it from the Bazaar purchase sibling 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?

The 'WHEN' clause names the trigger condition (buying a cosmetic with Arena play credits), names the alternative it is not (bazaar_shop_buy with Bazaar Credits), and routes the agent to the follow-up tool arena_cosmetics_equip. Alternatives and sequencing are both explicit.

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.