Skip to main content
Glama

cpu_start_mining

Start a bounded mining job on a cell with a finished extractor. Specify the number of cycles and optionally a target resource; the job runs until cycles complete or deposit dries up.

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. Costs no $CPU. 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 discloses important traits: costs no CPU, job is non-cancellable, holds process slot, cannot demolish mid-job, does not overrun, and effects on other operations. This is thorough and beyond the minimal.

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 detailed but well-organized, starting with the action and prerequisites, then explaining behavior. It could be slightly more concise, but every sentence adds value. No redundancy.

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?

The description covers all aspects: prerequisites, side effects (cell slot lock), scheduling advice, and references to related tools (cpu_get_mining_status, cpu_claim_mining). No output schema, but the return value is implied through tracking tools. Complete for a complex operation.

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?

The input schema has 100% coverage with detailed descriptions. The tool description adds context (e.g., 'batches is a commitment you cannot undo', 'omit targetResourceId when extractor mines a single resource'), enhancing understanding beyond the schema alone.

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 action: 'Start a bounded extraction job on a cell you own that holds a finished extractor.' It uses specific verbs and resources, and distinguishes from siblings like cpu_claim_mining and cpu_get_mining_status.

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 mentions prerequisites: session via cpu_authenticate, cell ownership, finished extractor, and building construction. It also gives guidance on when to omit targetResourceId and advises checking cpu_get_game_config and cpu_get_cell beforehand. It does not explicitly list when not to use it, but provides sufficient context for decision-making.

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