Skip to main content
Glama

cpu_list_cell

List one of your Cells on the NFT marketplace at your price; the call handles approval, signing, and fee split, and returns the order hash.

Instructions

Publish ONE Cell of yours for sale on the NFT marketplace, in a single call. This is the land market — Cells traded as NFTs for a configured currency — and it is entirely separate from cpu_create_lot, which sells RESOURCES for $CPU inside the game. The call performs the whole action itself: it checks that you are not about to duplicate an order, prepares the order, sends any collection approval your wallet still owes and waits for each receipt, signs the order locally, and publishes it. There is nothing to confirm afterwards. That collection approval is setApprovalForAll: a persistent operator grant over every Cell your wallet holds, not over the one Cell you are listing. It is sent once and then stays in force. price is the GROSS amount a buyer pays, as a base-unit decimal integer STRING (never a number). The marketplace and creator fees are mandatory and come out of that amount: calling this tool authorizes that split, and the result reports platformFee, creatorFee and estimatedProceeds so you can see it. There is no minimum-proceeds input. Pass buyerAddress to reserve the listing for exactly one wallet; pass null to let anyone buy it. The seller is always the authenticated wallet. Retrying is safe: an identical repeated call resumes the same prepared order instead of publishing a second one. If a listing of yours at the same Cell, price and expiry is already active, the call fails with ACTIVE_ORDER_EXISTS rather than duplicating it — cancel that order first if you meant to replace it. The result reports status (completed, or already_completed when the order proved to be published already), the published listing with its orderHash, the fee split, and every approval transaction hash in the order it was broadcast.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priceYesThe gross amount a buyer pays, as a positive decimal integer of the currency base units — never a decimal fraction. Marketplace and creator fees are taken out of this amount; the call returns the split and your estimated proceeds.
tokenIdYesThe Cell to sell, as a decimal token id with no leading zeroes (e.g. "0" or "1234", never "01234"). You must own it.
buyerAddressNoReserve the listing for exactly one buyer by passing their address; pass null (or omit it) to let anyone buy it. This never changes which wallet sells — that is always the authenticated wallet.
expirationTimeYesThe Unix second at which the listing stops being fillable. It must be in the future.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stageYes
statusYes
walletYes
listingYes
tokenIdYes
currencyYes
eventTypeYes
creatorFeeYes
grossPriceYes
platformFeeYes
approvalTxHashesYes
estimatedProceedsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.13.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and excels: it discloses the full multi-step side effects (approval, order preparation, local signing), the persistent setApprovalForAll grant affecting all Cells, fee deduction, retry safety, and failure behavior. This is exceptional transparency for a mutating marketplace operation.

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?

The description is long but dense and well-organized, front-loading the core purpose and then covering side effects, parameters, retry behavior, and result shape. Almost no filler, though it could be slightly trimmed without losing value.

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?

Given the tool's complexity, the description is remarkably complete: it covers the full execution flow, approval consequences, fee split, retry idempotency, error condition, and result fields. With the output schema present, an agent has everything needed to call this tool correctly and understand its consequences.

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 coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema: price is explicitly 'GROSS' with mandatory fees deducted, buyerAddress reservation semantics, and the seller being the authenticated wallet. This enriches the parameter understanding without replacing the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Publish ONE Cell of yours for sale on the NFT marketplace'), immediately clarifying what the tool does. It also explicitly contrasts itself with cpu_create_lot ('sells RESOURCES for $CPU inside the game'), making its distinct purpose unmistakable.

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?

The description clearly identifies the primary alternative (cpu_create_lot) and explains why this tool is different. It also gives concrete guidance on buyerAddress (reserve vs public) and when the call will fail (ACTIVE_ORDER_EXISTS). It does not enumerate all possible alternatives such as cpu_buy_cell or cpu_accept_cell_offer, but the core usage context is unambiguous.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/projectcpu/project-cpu-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server