Skip to main content
Glama

create_lot

List resource units for sale at a Hub by specifying a transport route, resource ID, quantity, and price per unit. Returns a lot ID for tracking.

Instructions

List units of a resource for sale at a Hub. Requires a session — call authenticate first. Transports the goods from your source cell to the listing Hub (chain = [source, ...waypoints, hub]) and opens a lot at pricePerUnit $CPU. A route over only your own cells is free and starts immediately; a route through a foreign Hub costs $CPU — this tool then auto-approves the $CPU spend once and submits the on-chain payment. Returns the lotId — track it with list_my_lots / get_lot. While a prior paid listing of the same resource from the same cell is still awaiting payment, a new one is rejected — finish or let the pending one lapse (a lapsed escrow is auto-refunded within ~a minute).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYes[source, ...waypoints, hub] in axial hex — first node is your source cell, last is the listing Hub. A route through a foreign Hub is paid in $CPU; the API validates the physics.
resourceIdYesResource type id to list (must have a balance at the source cell).
valueYesUnits to list, as a positive integer string.
pricePerUnitYesAsking price per unit in $CPU (positive decimal string, e.g. "0.5"). Must be > 0.
Behavior5/5

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

With no annotations, the description provides full disclosure: requires session, transports goods, costs CPU, auto-approves, returns lotId, and explains pending listing restriction with auto-refund for lapsed escrow. No contradictions.

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?

Packs essential information in a few sentences. Front-loaded with main purpose and prerequisite. Could be slightly more concise but every sentence adds 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 4 parameters, no output schema, the description explains return value (lotId) and tracking tools, covers constraints (pending listing, route cost), and lifecycle (auto-refund). Complete context for invocation.

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%, but the description adds meaning: chain is 'source, waypoints, hub' with validation; resourceId requires balance; value is positive integer; pricePerUnit > 0. Enriches schema without repetition.

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 'List units of a resource for sale at a Hub.' This specifies the verb (list) and resource (units for sale), and distinguishes from sibling tools like buy_lot, list_lots, etc.

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?

Explicitly states prerequisite (must call authenticate first), explains when a new listing is rejected (pending prior paid listing), and advises to use list_my_lots/get_lot for tracking. Also mentions conditions for route cost and auto-approval.

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

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