Skip to main content
Glama

cpu_get_mining_status

Check a cell's mining status including extractor activity, resource type, batch progress, claimable units, and whether mining is stalled due to warehouse cap.

Instructions

Read a cell's mining status: whether an extractor is active, which resource it mines, its per-cycle batch and cycle length, the units claimable now (whole matured cycles), the seconds until the next batch, the remaining deposit, and whether mining is stalled because that resource's warehouse hit its storage cap. Mining matures in whole cycles — a cycle in progress banks nothing until it completes. Production halts at the cap until you offload — transport it out, sell via create_lot, craft with it, or withdraw wCPU; a null cap means the warehouse is uncapped. When stalled, claimable reflects the remaining warehouse room (near zero on a full box). Public — works for any cell, no session required. The owner banks matured batches with cpu_claim_mining.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenIdYesThe tokenId of the cell to inspect mining for.
Behavior5/5

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

With no annotations provided, the description fully discloses the tool's behavior: mining matures in whole cycles, a cycle in progress yields nothing until completion, production halts at storage cap, and stalled behavior affects claimable. It also explains how to resolve stalls. This is highly transparent.

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 compact for the amount of information it conveys. It front-loads the purpose and then explains concepts like maturation and stall. It could be slightly more concise, but the structure is logical and each 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 the complexity of mining status and the absence of an output schema, the description provides a complete explanation of all returned fields, the mining cycle behavior, stall conditions, and how claimable is affected. It also mentions the sibling tool for claiming. No gaps remain for an agent to understand the tool's functionality.

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

Parameters3/5

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

The input schema has 100% coverage for the single parameter `tokenId`, with a clear description. The tool description does not add extra meaning beyond the schema for this parameter. Baseline for full coverage is 3, and no additional value is provided.

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 'Read a cell's mining status' with a specific verb and resource. It distinguishes itself from the sibling tool `cpu_claim_mining` by noting that the owner uses that tool to bank matured batches. The description enumerates all returned fields, making the tool's purpose very clear.

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 indicates that the tool is public, works for any cell, and requires no session, which helps an agent understand when to use it. It also contrasts with `cpu_claim_mining` for claiming matured batches. However, it does not explicitly state when not to use this tool or compare it to other related tools like `cpu_get_cell`.

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