Skip to main content
Glama

cpu_start_mining

Start a bounded mining run on a cell with a finished extractor. Pass a target resource and batch count to extract for a fixed number of cycles, with no cancel option.

Instructions

Start a bounded extraction job on a cell you own that holds a finished extractor. Requires a session — call cpu_authenticate first. Pass the targetResourceId to mine — it must be a resource the extractor can mine (see cpu_get_game_config) with an active deposit on the cell; omit it when the extractor mines a single resource. Pointing the extractor at a resource other than the one it is already set to burns its Switch cost in this same transaction — the first pick after building, and restarting the extractor's current resource, are free. Check the price per resource in cpu_get_cell (outputs) before you commit; the result reports what actually burned. The building must have finished construction — building takes time after cpu_build. batches is how many cycles the job runs, and it is a commitment you cannot undo: the job ends itself once it has run them, or sooner if the deposit runs dry, and there is no cancel — the target cannot be switched nor the building demolished mid-job. It never overruns its schedule, so coming back late banks exactly what you booked and no more. Until the job ends it holds the cell's only process slot, so nothing can be crafted there; claiming a finished job frees the slot. Size batches against the cycle length in cpu_get_game_config and the deposit in cpu_get_cell — scheduling past the deposit just ends early. Track it with cpu_get_mining_status and bank matured cycles with cpu_claim_mining.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
batchesYesHow many cycles to run, 1..1000. The job stops itself after these — it never produces past them, so arriving late banks exactly what was scheduled, no more. There is no cancel: restarting costs a claim plus a new start. Read the cycle length from cpu_get_game_config and size the run to how long you want the cell committed.
tokenIdYesThe tokenId of a cell you own holding a finished extractor.
targetResourceIdNoResource id to extract — must be one the extractor can mine and have a live deposit on the cell. Omit (null) to auto-pick when the extractor mines a single resource.
Behavior5/5

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

With no annotations provided, the description fully carries the burden and does so thoroughly. It discloses the switch cost behavior, free first pick/restart, no-cancel commitment, process slot locking, schedule never overruns, early end on dry deposit, and the need to wait for construction completion. This is rich, non-obvious behavioral context.

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 each sentence adds unique value. It is well-structured: starts with the core action, then prerequisites, then parameters, then consequences and tracking. No fluff or repetition; the length is justified by the tool's 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 tool's complexity (no output schema, no annotations), the description is remarkably complete. It covers prerequisites, parameter semantics, edge cases (switch cost, dry deposit, process slot), and post-actions (tracking and claiming). An agent has everything needed to invoke 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?

Schema coverage is 100%, so the baseline is 3, but the description adds significant meaning beyond the schema. For targetResourceId, it explains the switch cost and the omit-if-single-resource rule. For batches, it stresses commitment and sizing against cycle length and deposit, which the schema already hints at but the description enriches with strategic guidance.

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: 'Start a bounded extraction job on a cell you own that holds a finished extractor.' This clearly distinguishes the tool from sibling mining tools like cpu_claim_mining and cpu_get_mining_status by focusing on the action of starting a job.

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?

Provides clear guidance: requires a session (call cpu_authenticate first), references cpu_get_game_config for cycle lengths and cpu_get_cell for checking deposit/outputs, and points to cpu_get_mining_status and cpu_claim_mining for tracking and claiming. It doesn't explicitly state 'when not to use' but effectively covers the context and associated tools.

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