Skip to main content
Glama

cpu_create_lot

List resource units for sale at a Hub in one transaction: ship goods from your cell, set a price per unit, and optionally cap the max sale fee. Returns a lot ID.

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 charges a sale fee on every sale, carved out of the seller proceeds (the buyer still pays exactly price × value). maxSaleFeePercent is your tolerance: the highest rate you accept — omit it to lock in the live rate at listing (read on-chain). The hub settles its live rate each sale (never above your tolerance); if it later rises above the tolerance the lot freezes and buys revert until the hub lowers it — cpu_cancel_lot is always fee-free and returns the escrow. 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 locked-in maxSaleFeePercent; 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–100) you accept the hub charging on each sale. Omit to lock in the hub's live rate at listing time as the tolerance. The hub settles its live rate on every sale (never more than the tolerance); if the owner later raises it above the tolerance the lot freezes — buys revert until the rate drops back to the tolerance or below — and cpu_cancel_lot is always fee-free.
Behavior5/5

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

With no annotations, the description fully discloses behavior: atomic transaction, state transition from DELIVERING to OPEN, fee mechanics (transit fee, hub sale fee), freezing condition when the hub raises its fee above tolerance, and that `cpu_cancel_lot` is always fee-free. It gives concrete details on what happens to the lot and escrow, going far beyond any structured metadata.

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

Conciseness5/5

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

The description is long but every sentence carries essential information for a complex tool. It is front-loaded with the main purpose, then efficiently covers mechanics, fees, states, and return values. There is no fluff; each sentence earns its place.

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 5-parameter complexity, no annotations, and no output schema, the description is remarkably complete. It explains return values (lotId and locked-in `maxSaleFeePercent`), the delivery finalization step, related tracking tools, and all fee/freeze edge cases. Nothing essential is missing for a competent agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the input schema already covers 100% of parameters, the description adds substantial contextual meaning beyond the schema. For `chain`, it explains the source-to-hub route and foreign hub fee; for `maxSaleFeePercent`, it details the tolerance, locking behavior, and freeze conditions; for `value` and `pricePerUnit`, it ties them to the sale fee model. This is added value, not redundancy.

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 clear, specific verb and resource: 'List units of a resource for sale at a Hub, on-chain.' It distinguishes this from sibling tools like cpu_buy_lot and cpu_cancel_lot by focusing on the creation of a sell lot with atomic shipping, and it explains the overall operation. The scope is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a prerequisite (needs `cpu_authenticate` first), explains when to use it (to list units at a hub), and references alternatives and follow-ups: `cpu_finalize_delivery`, `cpu_cancel_lot`, `cpu_list_my_lots`, `cpu_get_lot`. It also clarifies the transit fee condition and the hub fee tolerance, giving a complete usage scenario.

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

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