Skip to main content
Glama

cpu_create_lot

Create a lot to list resource units for sale at a Hub on-chain, specifying a route from source to Hub and a price per unit. The lot becomes buyable after escrow is finalized.

Instructions

List units of a resource for sale at a Hub, on-chain (needs a session — cpu_authenticate first). One atomic tx: ships the goods from your source cell to the listing Hub (chain = [source, ...waypoints, hub]) and opens a lot at pricePerUnit $CPU, plus gas. A route through a foreign Hub costs a $CPU transit fee (auto-approved once); over only your own cells it is free. The hub owner's current sale-fee rate is frozen into the lot and is later carved out of the seller proceeds on every sale (the buyer still pays exactly price × value). Optionally cap it with maxSaleFeePercent; omit it to accept the live rate at listing (read on-chain) — a last-moment rate raise then reverts the listing instead of freezing a worse rate in. The lot is DELIVERING and becomes buyable (OPEN) only after its escrow arrives — call cpu_finalize_delivery on the returned deliveryId (or wait). Returns the lotId and the frozen saleFeePercent; track with cpu_list_my_lots / cpu_get_lot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYesWaypoint tokenIds [source, ...waypoints, hub] — first node is your source cell, last is the listing Hub. A route through a foreign Hub is paid in $CPU. Scout waypoints with cpu_next_hops.
valueYesUnits to list, as a positive integer string.
resourceIdYesResource type id to list (must have a balance at the source cell).
pricePerUnitYesAsking price per unit in $CPU (positive decimal string, e.g. "0.5"). Must be > 0.
maxSaleFeePercentNoOptional seller tolerance: the highest sale-fee percent (0–50) you accept the hub charging. Omit to accept the hub's live rate at listing time — the listing then reverts if the owner raised the rate in the meantime, instead of freezing a worse rate into your lot.
Behavior5/5

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

No annotations are provided, so the description carries full burden. It thoroughly discloses behavioral traits: atomic transaction, shipping goods, opening lot, gas costs, transit fees, sale fee freezing, delivery state, and return values. It also explains edge cases like rate raises and maxSaleFeePercent behavior.

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 relatively long but well-structured. It front-loads the main purpose and prerequisite, then details parameters and behavior. Every sentence adds value, but there is slight redundancy (e.g., mentioning tracking tools twice). Still, it is concise given the complexity.

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 complexity (5 parameters, no output schema), the description is remarkably complete. It covers prerequisites, parameter semantics, process flow, edge cases (rate raises), and return values (lotId, saleFeePercent). It also mentions subsequent tracking tools, making it fully actionable.

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 100%, so baseline is 3. The description adds significant meaning beyond the schema: it explains the chain structure (first node source, last hub), value as 'units to list', resourceId needing balance, pricePerUnit must be >0, and maxSaleFeePercent's effect. This elevates the score above baseline.

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 clearly states the purpose: 'List units of a resource for sale at a Hub, on-chain'. It uses a specific verb (list) and resource (units of a resource) and distinguishes this from sibling tools like cpu_buy_lot and cpu_cancel_lot.

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 explicitly states the prerequisite: 'needs a session — cpu_authenticate first'. It also explains when to use the chain parameter and provides guidance on optional maxSaleFeePercent. However, it does not explicitly state when not to use the tool, though it is implied.

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

Install Server

Other Tools

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/sodiqit/project-cpu-mcp'

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