Skip to main content
Glama

locker_inventory

Read up to 100 most recent operator Locker purchases and recorded effects. pricePaid/effectValue are camelCase aliases; purchasedAt/consumedAt are ISO UTC timestamps (Z), with null when unconsumed. Legacy snake_case fields remain. Flavor/flair items have no manual effect use; resident tonic effects stay in existing game settlement.

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_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: a hard 100-record cap, null values for unconsumed items, and UTC ISO timestamp semantics. However it omits anything about permissions/auth, ordering guarantees, or whether pricePaid reflects pre- or post-discount amounts, which matters for a purchase-history read.

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?

Two sentences, front-loaded with the purpose and scope before moving to field semantics. The second half is dense domain jargon ('flavor/flair', 'resident tonic effects', 'existing game settlement') that takes effort to parse, but every clause conveys information an agent cannot get elsewhere.

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?

With no output schema, the description legitimately must explain the return shape, and it does so for aliases, timestamps, nullability, and legacy field retention. The remaining gap is the absence of any statement about ordering beyond 'most recent' and what the caller should do about the 100-record ceiling.

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 takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly spends no words on input arguments.

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 opening sentence names a specific verb and resource ('Read ... operator Locker purchases and recorded effects') plus a scope limit ('up to 100 most recent'). It clearly distinguishes itself from sibling locker_buy and locker_catalog by describing a read of historical purchases, though it never names those siblings explicitly.

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

Usage Guidelines2/5

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

The description gives no guidance on when to call this versus locker_catalog (browsing what's buyable) or inventory (owned items). It also doesn't say whether results are paginated, how to request older entries, or what happens when the operator has more than 100 purchases.

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