Skip to main content
Glama

locker_catalog

Browse Legend's Locker KBUX catalog and buyer scope. kbuxPrice, buyerScope and effectValue are camelCase aliases; legacy snake_case fields remain. Not a USD store or checkout; resident-only items cannot be bought with an operator wallet.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose meaningful behavior: field-name aliasing (camelCase aliases with legacy snake_case), buyer-scope limitations, and wallet restrictions. It does not explicitly say the operation is read-only or describe pagination, but 'Browse' strongly implies a read operation and the disclosed constraints are valuable.

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?

The description is three sentences and front-loads the primary purpose before adding field-alias details and exclusions. The alias sentence is somewhat dense but earns its place by clarifying field naming, and the overall text avoids unnecessary repetition.

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?

There is no output schema, so the description should provide return-context; it mentions key catalog fields and buyer-scope constraints, which gives an agent enough to understand what browsing yields. It stops short of fully describing the catalog entry structure, but the core context for a zero-parameter browse tool is present.

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?

The tool has zero parameters, so there is no parameter semantics burden; the baseline is 4. The description's discussion of output fields (kbuxPrice, buyerScope, effectValue) is not parameter-related but does not conflict with the empty schema.

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 states a specific verb (Browse) and resource (Legend's Locker KBUX catalog and buyer scope). It distinguishes the tool from checkout/buying with explicit exclusions, though it does not directly contrast with the sibling locker_buy or locker_inventory.

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?

The description says what the tool is not ('Not a USD store or checkout') and notes that resident-only items cannot be bought with an operator wallet, giving implied usage constraints. However, it does not explicitly name an alternative tool such as locker_buy for purchasing or state when to choose this over locker_inventory.

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