Skip to main content
Glama

Buy an item

hollow_buy

Buy items or services from a Super Store bay using RC from your passport, with a client-supplied order_id to prevent duplicate purchases on retry. For services, include your request in the note.

Instructions

Buy an item from a Super Store bay with RC from the passport. Pass your own order_id so a retry buys once; for a service, say in note what you want. Costs RC (100 RC = $1): refused until the owner starts the server with ETHER_HOLLOW_SPEND=1.

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": {
      "bay": "<bay>",
      "item": "<item>"
    },
    "name": "hollow_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
bayYesThe bay id or maker
itemYesThe item id
noteNoFor a service: what you want, plain words
order_idNoYour own id for this order, so a retry buys once

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations declare the tool is not read-only and touches an open world, and the description adds behavior the annotations cannot carry: real monetary cost (100 RC = $1) and an owner-set gate that makes spending fail until enabled. The order_id retry contract explains the idempotency model, which is useful because idempotentHint is false. It does not say what a successful purchase returns or whether delivery is immediate, but that is a minor gap for a tool of this size.

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?

Three compact sentences, front-loaded with what the tool does, then the retry contract, then the cost and gate. Every clause carries information an agent needs; nothing is padding.

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 should explain the result but does not: it never says what a successful purchase returns or how the order is confirmed. It does fully cover cost, the owner gate, and retry safety, which are the risky parts of a spend operation. Only the outcome side is left underspecified.

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 coverage is 100%, so all four parameters are already documented. The description mostly restates the order_id retry purpose and the note field's meaning for services, rather than adding syntax or edge cases. Baseline 3 is right here.

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?

States a specific verb and resource: buy an item from a Super Store bay, paid in RC from the passport. That is concrete enough to act on. It does not distinguish itself from the sibling hollow_buy_rc, so the scope boundary against a similarly named alternative is left implicit.

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?

Gives real usage guidance: supply your own order_id so a retry buys only once, and use the note field to describe what you want when buying a service. It also states the precondition that spending is refused until the owner starts the server with ETHER_HOLLOW_SPEND=1. It stops short of saying when to pick this tool over an alternative, but the context it does give is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.