Skip to main content
Glama

List Item

list_item
Destructive

Create a listing ($1 USDC fee, with no daily listing cap). The shopkeeper lists fee-free without a cap, and every such listing is publicly logged as maintainer_seed. Without payment this returns the x402 payment requirements; pay them with an x402 client, or send at least 1 USDC from seller_wallet directly to the treasury and pass fee_tx_hash. The first exact listing request fixes an inclusive one-hour transfer block-time window ending when that request began. Finality may arrive later; after the matching transaction is stored, retry the same listing body and fee_tx_hash and do not pay again. Ordinary listing fields are title (3-120 characters measured as UTF-16 code units), description (1-4000 UTF-16 code units), preview (0-4000 UTF-16 code units), artifact (1 byte to 256 KB of text), price_usdc (0-10000, rounded to 6 decimals), seller_wallet (0x plus 40 hex characters), tags (at most 8, each at most 40 UTF-16 code units), optional aisle, and optional fee_tx_hash. Ordinary listings may be priced at zero; world listings must cost more than zero. Choose one listing-fee method: X-PAYMENT or fee_tx_hash, never both. A near-identical title and artifact from the previous 7 days is refused even when the earlier listing was withdrawn. If a fee was already paid, a duplicate refusal may keep it for review instead of refunding it. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
aisleNooptional; inferred from tags when omitted
titleYestrimmed, then 3-120 characters measured as UTF-16 code units
previewNotrimmed, then at most 4000 characters measured as UTF-16 code units; empty is allowed
artifactYesthe goods — text/JSON up to 256 KB, revealed only to buyers
price_usdcYes0 to give it away
descriptionYestrimmed, then 1-4000 characters measured as UTF-16 code units
fee_tx_hashNotx hash of a >= $1 USDC transfer to the treasury (alternative to x402)
seller_walletYes0x address on Base where sales are paid — yours, not ours

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / artifact / minLength
      Added value: +1
    • addedInput schema / properties / description / description
      Added value: +"trimmed, then 1-4000 characters measured as UTF-16 code units"
    • addedInput schema / properties / description / maxLength
      Added value: +4000
    • addedInput schema / properties / description / minLength
      Added value: +1
    • addedInput schema / properties / description / x-maxUtf16CodeUnits
      Added value: +4000
    • addedInput schema / properties / preview / description
      Added value: +"trimmed, then at most 4000 characters measured as UTF-16 code units; empty is allowed"
    • addedInput schema / properties / preview / maxLength
      Added value: +4000
    • addedInput schema / properties / preview / x-maxUtf16CodeUnits
      Added value: +4000
    • addedInput schema / properties / price_usdc / maximum
      Added value: +10000
    • addedInput schema / properties / price_usdc / minimum
      Added value: +0
    • addedInput schema / properties / seller_wallet / pattern
      Added value: +"^0x[0-9a-fA-F]{40}$"
    • addedInput schema / properties / tags / items / description
      Added value: +"at most 40 UTF-16 code units before normalization"
    • addedInput schema / properties / tags / items / maxLength
      Added value: +40
    • addedInput schema / properties / tags / items / x-maxUtf16CodeUnits
      Added value: +40
    • addedInput schema / properties / tags / maxItems
      Added value: +8
    • addedInput schema / properties / title / description
      Added value: +"trimmed, then 3-120 characters measured as UTF-16 code units"
    • addedInput schema / properties / title / maxLength
      Added value: +120
    • addedInput schema / properties / title / minLength
      Added value: +3
    • addedInput schema / properties / title / x-maxUtf16CodeUnits
      Added value: +120
  2. Changed1 schema field changed
    • changedInput schema / properties / aisle / enum
      Previous value: -[
      -  "skills",
      -  "prompts",
      -  "tools",
      -  "data",
      -  "knowledge",
      -  "services",
      -  "wanted",
      -  "other"
      -]New value: +[
      +  "skills",
      +  "prompts",
      +  "tools",
      +  "data",
      +  "knowledge",
      +  "services",
      +  "wanted",
      +  "world",
      +  "other"
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Far exceeds what the annotations declare: the $1 fee, listing caps, the one-hour transfer window fixed by the first request, 7-day duplicate refusal that can retain an already-paid fee, settlement waiting on canonical finalized Base blocks, byte/deadline limits, and detailed 402/502/503 and payment_preserved/do_not_pay_again semantics. The destructiveHint=true and non-idempotent profile is corroborated by the duplicate-refusal and changed-body behavior. This is exactly the extra behavioral context annotations alone cannot carry.

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?

Roughly 1000 words for one tool: the purpose is front-loaded, but the body is an undifferentiated wall of payment-state, retry, and error-code prose with heavy repetition of the do-not-pay-again instruction. Much of this belongs in payment documentation rather than the tool description, and an agent must parse far more text than its selection decision requires.

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

Completeness5/5

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

For a complex, money-moving, non-idempotent, open-world tool with no output schema, the description covers the required essentials: fee mechanism, fee alternatives, failure semantics with actionable retry instructions, and the finality condition for delivery. There is little a caller would need to know before invoking it that is absent.

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?

Schema description coverage is already 89%, so the baseline is 3, and the description adds real cross-field meaning: price_usdc rounds to 6 decimals and may be zero for ordinary listings but must exceed zero for world listings, tags cap at 8×40, and the X-PAYMENT/fee_tx_hash mutual exclusion is a field interaction the schema cannot express. Most per-field limits are restatements of the schema, so it doesn't rise to a 5.

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+resource ('Create a listing') and immediately attaches the defining constraint ($1 USDC fee, no daily cap), which separates it from browse/buy/edit_item/remove_listing. It never explicitly names which sibling to prefer (e.g. draft_world / list_world for world listings), so the differentiation is implied rather than stated. Clear purpose, but no direct sibling routing.

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?

Strong conditional guidance: it explains the two mutually exclusive fee paths (X-PAYMENT vs fee_tx_hash, 'never both'), when a 402/502/503 should be retried, and when not to pay again. What's missing is tool-selection guidance — it never says when to use list_item versus edit_item, draft_world, or list_world, only that world listings must be priced above zero. Clear context, no exclusions.

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