Skip to main content
Glama
projectcpu

project-cpu-mcp

by projectcpu
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

cpu_get_map

Read the live world state of Project CPU to navigate cells, monitor storage, and plan resource production.

Instructions

Read the live game world (public, background-synced). The world is a finite sphere of 29,150 cells keyed by tokenId — no coordinates: navigate via each cell’s neighbors (6 adjacent, 5 next to a pentagon vertex; owned/other/empty, empty = unminted) and cpu_next_hops; pos {face,i,j} is only a rough hint (wraps at face seams). Returns a summary, a resourceIndex of your cells, and per-resource storage (used/cap/full; a box with room for less than one whole cycle halts that resource’s production; cap null = uncapped WCPU, while every other missing/zero cap means no room). Scopes: mine | around (grid radius from aroundTokenId) | cells | all | summary. version/updated are epoch ms, serverTime/startAt unix seconds. server.reachable false means actions will fail; your to-do list is cpu_get_attention. This is land and storage, not the marketplace: storage.reserved.lots is how much of a hub box lot escrow holds, never an offer you can buy. For offers use cpu_get_markets and cpu_list_lots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNomine | around | cells | all | summary. Omit to default to "mine" (or "summary" if no wallet).
radiusNoGrid radius (BFS steps) for scope="around" (default 2, max 10).
tokenIdsNoRequired for scope="cells": the cell tokenIds to return.
aroundTokenIdNoCenter cell tokenId for scope="around".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.10.0
    • changedInput schema / properties / aroundTokenId / anyOf
      Previous value: -[
-  {
-    "maximum": 48990,
-    "minimum": 1,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 29150,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observedv0.8.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it delivers: read-only nature, tokenId-based navigation without coordinates, neighbor semantics, empty=unminted, storage cutoff behavior, nullable cap semantics, scopes, time unit differences, and server.reachable implications. This is dense, honest behavioral disclosure.

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 long but information-dense; every clause adds value, especially given no annotations or output schema. It is front-loaded with the core action, though the single dense paragraph could be marginally easier to parse with light structural separation.

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?

There is no output schema, so the description must explain returns, and it does: summary, resourceIndex, per-resource storage fields, epoch vs unix time, scopes, and failure behavior. For a complex 4-parameter tool with all-optional inputs, nothing essential is missing.

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?

Schema coverage is 100%, so the schema already documents each parameter. The description adds a useful default nuance ("mine" vs "summary" if no wallet) and recontextualizes tokenIds within the map model, but most parameter meaning is already carried by the schema.

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: "Read the live game world." It then differentiates this tool from marketplace tools by explaining it is "land and storage, not the marketplace," making its purpose unmistakable even among many sibling tools.

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?

The description explicitly directs when to use alternatives: "For offers use cpu_get_markets and cpu_list_lots" and points to cpu_get_attention for action items. It also clarifies scopes and defaults, so an agent knows how to select the right mode rather than guessing.

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