Skip to main content
Glama

List World

list_world
Destructive

Activate a world draft after the city publicly proves the thing is yours and locked. Every merchant except the shopkeeper pays the normal $1 USDC listing fee; a direct fee transfer may be larger but must be at least $1. The shopkeeper lists fee-free without a cap, logged as maintainer_seed. A direct fee uses the same fixed one-hour block-time window and exact-body retry rules as list_item. Never put a city bearer secret in arguments. A remnant cannot be offered in the city; a thing with an end set can, and its card shows the end. Exactly these fields, nothing else: draft_id, city_offer_id, and optional fee_tx_hash. A 402 means payment is required or the proof is known to be invalid. A 502 means the facilitator rejected a request without identifying whether the proof, the market's requirements, or facilitator handling was at fault; do not replace or replay the proof blindly. A terminal refusal with an unrecognized caller-correctable cause is 502; do not retry or replay that proof blindly. A 503 means payment or chain verification is unavailable, including an explicit facilitator failure that did not match a known caller mistake; retry the same proof. payment_preserved:false means no direct fee or claim transaction was stored: check the wallet and retry that same proof inside its original window instead of blindly paying again. do_not_pay_again:true means the market stored or may have settled that payment; follow only the exact retry action in the response. For x402, the verified proof and exact paid request are saved before the facilitator is asked to settle. Once saved, retry the same endpoint with the same body; omit X-PAYMENT when do_not_pay_again is true, and never create or pay a replacement proof. Delivery waits until the exact transfer is in a canonical finalized Base block. Changing a paid listing body creates a different request that the saved payment cannot satisfy. X-PAYMENT is limited to 16000 bytes before JSON parsing, Base or facilitator calls, or custody writes. Each facilitator response is limited to 65536 bytes while streaming, and each request has a 8-second deadline. A verification timeout happens before settlement starts: retry the same request with the same proof. A settlement timeout may leave the result uncertain: retry the same endpoint and body, omit X-PAYMENT when do_not_pay_again is true, and do not pay again. A confirmed X-PAYMENT-RESPONSE contains only the normalized receipt and is capped at 512 bytes. A pending or duplicate settlement is 503; retry the same proof and do not pay again.

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": {
      "draft_id": "<draft_id>",
      "city_offer_id": "<city_offer_id>"
    },
    "name": "list_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYes
fee_tx_hashNooptional proof of a direct fee of at least $1 USDC sent to the official treasury
city_offer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / city_offer_id / maximum
      Added value: +2147483647
    • addedInput schema / properties / city_offer_id / minimum
      Added value: +1
    • changedInput schema / properties / city_offer_id / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / draft_id / maximum
      Added value: +2147483647
    • addedInput schema / properties / draft_id / minimum
      Added value: +1
    • changedInput schema / properties / draft_id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / fee_tx_hash / description
      Previous value: -"optional proof of a direct $1 treasury fee"New value: +"optional proof of a direct fee of at least $1 USDC sent to the official treasury"
    • addedInput schema / properties / fee_tx_hash / pattern
      Added value: +"^0x[0-9a-fA-F]{64}$"
  2. Added

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, but the description goes well beyond them: fee amounts and who pays, maintainer_seed logging, a one-hour block-time window, bearer-secret handling, byte caps on X-PAYMENT and facilitator responses, an 8-second deadline, and explicit 402/502/503 semantics. It also spells out what a failure preserves (payment_preserved:false, do_not_pay_again:true) and the exact retry action for each, which is exactly the behavioral context a destructive paid tool needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is one sentence, then a long wall of payment mechanics follows with substantial repetition: the 402/502/503 paragraph, the x402 paragraph, and the timeout paragraph restate the same "retry the same proof, omit X-PAYMENT, do not pay again" rule three times. Structure is a flat run-on rather than front-loaded sections, so the essential operation and the conditional detail are hard to separate.

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 destructive, paid, open-world mutation with no output schema, the description covers prerequisites, fees, retry/replay safety, and resource limits thoroughly. The remaining gap is the success side: it never says what activation produces or what the resulting listing looks like, and "the city publicly proves the thing is yours and locked" is never unpacked into a concrete procedure.

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 description coverage is only 33%, and the description's contribution is limited to "Exactly these fields, nothing else: draft_id, city_offer_id, and optional fee_tx_hash," which largely restates additionalProperties:false and the schema. It does add meaning for fee_tx_hash ("a direct fee transfer may be larger but must be at least $1"), but draft_id and city_offer_id — including what a city_offer_id even is — remain unexplained.

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 gives a specific verb and resource: "Activate a world draft after the city publicly proves the thing is yours and locked." That is far more informative than the misleading name/title ("List World" sounds like enumeration). It distinguishes itself implicitly from draft_world and cancel_world_draft by being the activation step, though it never names those siblings directly.

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 precondition (city proves ownership and the thing is locked) and the fee branches (merchant pays $1, shopkeeper fee-free as maintainer_seed) give real when-to-use context. However, it never routes the agent explicitly among the numerous siblings (checkout_world, sync_world, list_item) beyond borrowing list_item's retry rules, so selection guidance is implied rather than stated.

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