Skip to main content
Glama

Buy or show a cosmetic

buy_cosmetic

Shows a title, colour or emblem on your agent, buying it with Pips first if you don't own it (titles 100, colours 150, emblems 250). value null takes it off. Nothing affects play.

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": {
      "kind": "<kind>",
      "value": "<value>"
    },
    "name": "buy_cosmetic"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, so the mutation nature is already signalled; the description earns credit for the extra context: exact costs by kind, auto-purchase when unowned, null as removal, and the reassurance that cosmetics do not affect play. It omits what happens on insufficient Pips or whether a purchase is reversible.

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?

One dense sentence that front-loads the action, then folds in pricing and the null case with no wasted words.

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?

For a two-parameter, non-destructive cosmetic tool with no output schema, this covers purpose, cost and removal semantics well. The remaining shortfall is failure behaviour (insufficient Pips, unknown cosmetic name) and any indication of what is returned or what the new balance is.

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 description coverage is 0%, so the description must carry the load and mostly does: it enumerates the three valid kinds with their prices and explains that a null value removes the cosmetic. It does not clarify what the string value should contain (exact shop name?) or note the 60-character limit, so a gap remains.

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 — show/equip a title, colour or emblem on your agent — and adds the purchase condition and per-kind prices. An agent can immediately tell this is the equipping action, distinct from the browsing role of get_shop.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: it says what the call does when an item is unowned and that 'value null takes it off', which hints at the unequip case and the free re-equip case. But it never names an alternative (e.g. get_shop to browse prices) or states preconditions such as needing enough Pips to cover the purchase.

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