Skip to main content
Glama

Buy RC

hollow_buy_rc

Get the town's answer on how to buy RC with real money, including the payment method to use. Use it to learn the purchase route before spending (100 RC = $1).

Instructions

Ask the town how to buy RC with real money; the answer carries the way to pay. Nothing is charged by this call itself. Costs RC (100 RC = $1): refused until the owner starts the server with ETHER_HOLLOW_SPEND=1.

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

Input Schema

NameRequiredDescriptionDefault
response_formatNo"markdown" for readable text (the default), "json" for the town's whole answer as structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark it non-read-only and open-world, and the description adds real context beyond them: nothing is charged by the call itself, the answer carries the payment path, and the exchange rate is 100 RC = $1. The gap is that it never says whether the call records an intent/order (consistent with readOnlyHint=false), and 'Costs RC (100 RC = $1)' blurs whether the cost is in-game currency or real money.

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?

Three short sentences, front-loaded with the core action, then the no-charge caveat, then the cost/gating condition. No filler, though 'the answer carries the way to pay' is a slightly cryptic way to describe the return value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter inquiry with no output schema and annotations present, the description covers the gate, cost, and no-charge semantics but omits what the response actually contains and what the caller should do next with the payment route, leaving the end-to-end flow 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?

Only one optional parameter exists and its schema description coverage is 100%, so the enum values for response_format are already fully documented. The description adds nothing about the parameter, which is acceptable at baseline but no more.

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 gives a concrete verb and object ('Ask the town how to buy RC with real money') and importantly corrects the misleading name/title by clarifying that this call does not itself purchase anything. It lets an agent separate it from hollow_buy, though it never names that sibling or any alternative.

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?

It states a hard prerequisite (refused until the owner starts the server with ETHER_HOLLOW_SPEND=1), which is genuine when-to-use guidance, but it never says when to prefer this over hollow_buy or hollow_agreement, nor what to do after receiving the payment route.

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