Skip to main content
Glama

cpu_get_attention

Retrieve a prioritized list of cells needing attention, from critical stalls to warnings and info, filtered by urgency and owner. Skip full map scans by focusing on time-sensitive issues.

Instructions

Owner-scoped roll-up of cells worth attention, most time-sensitive first — so you skip scanning the whole map. Flags, each with a severity: stalled mining/craft (the output box has room for less than one whole cycle, so nothing settles and the wait burns — critical); a near-full warehouse on an actively-produced resource, a job that has run its scheduled cycles and now idles the cell until claimed, an arrived delivery ready to finalize, or an extractor on a depleted deposit (warning); revealed-but-unbuilt cells, and cells in a post-demolish rebuild cooldown (info — on a demolish_cooldown item arrivalAt marks when rebuild reopens). A finished job loses nothing by waiting, unlike a stall — it only holds the cell idle. Items are purely descriptive (cell, resource, used/cap breakdown, deposit, delivery) and suggest no action — you decide. Your own cells need an authenticated wallet; pass owner to scout another player read-only (all data is public). minSeverity filters by urgency. If the deliveries endpoint is down, map items still return and a note says so.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerNoScout another player: their wallet address to inspect their cells (read-only intel — the map is public). Omit to get your own to-do list. Deliveries are only surfaced for yourself.
minSeverityNoOnly return items at or above this urgency (critical > warning > info). Default: all.
Behavior5/5

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

With no annotations, the description carries full burden. It discloses that items are descriptive ('suggest no action'), scouting is read-only, authentication needed for own cells, and potential unavailability of deliveries. It details flags and severity levels comprehensively.

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 dense but well-structured, starting with purpose then detailing flags and usage. While packed with information, some sentences are long; slight trimming could improve conciseness.

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 no output schema, the description adequately describes return items (flags with severity, descriptive objects). It covers edge cases like deliveries down. The tool's complexity is well-handled.

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%, baseline 3. The description adds meaning: owner parameter scope (own vs scout) and minSeverity as urgency filter. It provides context beyond the schema's basic descriptions.

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 what the tool does: 'Owner-scoped roll-up of cells worth attention, most time-sensitive first'. It distinguishes itself from siblings like cpu_get_cell or cpu_get_map by focusing on attention-worthy items.

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 explains when to use ('so you skip scanning the whole map') and covers scoping (own cells vs scout another). It provides a note about deliveries endpoint downtime. However, it doesn't explicitly state when not to use the tool.

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