Skip to main content
Glama

cpu_next_hops

Survey legal next waypoints from a cell, listing each eligible hop with distance, owner, hub status, and transit fee, plus compass distance toward an optional destination.

Instructions

Survey the legal next waypoints from a cell (read-only). Lists every eligible waypoint — your revealed cells and every finished Hub — within one hop under the reach rule: hop ≤ radius(from)+radius(to)−1 grid steps (default balance: own↔own 1 = adjacent only, own↔hub 3, hub↔hub 5). A Hub counts only once its construction finishes: until then it grants no hub reach and charges no fee, and a foreign one is no waypoint at all — fromReady says whether your own origin is still building, which is why its reach may be smaller than you expect. Foreign cells are never waypoints, so even a single foreign cell between two plain cells is a WALL — only a finished Hub reaches across; empty hops means goods can only be hauled up to here. Facts per candidate: hop distance, owner, hub flag, ready build state, the exact per-unit transit fee for your resourceId cargo, and — with towards — the remaining grid distance (a compass, not a route). Planning is YOUR job: pick each hop yourself (cheap vs short vs whose hub you trust), chain them into path, and verify with cpu_quote_transport. To break a wall: build a border Hub (it still needs an eligible landing cell within reach on the far side), buy land across, or go around. WHEN: the cheap point check — call it right before each leg and after cpu_get_changes shows movement (hubs get demolished, fees change while goods travel); replan via cpu_route_network only when a local fix is impossible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesThe cell to hop from (your revealed cell, or a Hub).
towardsNoOptional destination — adds the remaining grid distance to it for each candidate (a compass).
resourceIdYesThe cargo resource id — each candidate hub shows its exact per-unit transit fee for it.
Behavior5/5

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

No annotations are provided, so the description carries full burden. It describes read-only nature, reach rules, hub states (fromReady), how fees are computed, and that empty hops indicate a wall. It fully discloses what happens in different scenarios.

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 thorough but somewhat long. However, every sentence adds value, and the key purpose is front-loaded ('Survey the legal next waypoints from a cell (read-only)'). Could be slightly more compact, but effectively structured.

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?

No output schema is provided. The description explains exactly what is returned: hop distance, owner, hub flag, ready state, per-unit transit fee, and remaining grid distance if 'towards' is given. It also explains the meaning of empty list. Thorough for this tool.

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%, setting baseline at 3. The description adds value by explaining that 'from' can be a cell or hub, 'towards' adds remaining grid distance as a compass, and 'resourceId' determines per-unit fee. This context goes beyond the schema 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 the tool 'surveys the legal next waypoints from a cell (read-only)'. It uses specific verbs and distinguishes from the sibling tool 'cpu_route_network' by noting that local planning is the user's job and that replanning via the sibling is only for when local fixes are impossible.

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 tells when to call: 'the cheap point check — call it right before each leg and after cpu_get_changes shows movement'. It also specifies when not to use and alternatives: 'replan via cpu_route_network only when a local fix is impossible' and explains that foreign cells are not waypoints.

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