Skip to main content
Glama

cpu_next_hops

List eligible next hops from any cell under the reach rule, showing distance, ownership, hub status, build state, and transit fees to plan and chain cargo waypoints.

Instructions

Survey the legal next waypoints from a cell (read-only). Lists every eligible waypoint within one hop under the reach rule: hop ≤ radius(from)+radius(to)−1 grid steps. Eligible means Virgin ground (isVirgin — no completed reveal yet, minted or not, owner null when nobody has minted it), any cell you own, or any cell carrying a finished Hub, foreign ones included. Only foreign land past its first completed reveal without a finished Hub is closed — that, not open ground, is the WALL: a belt of foreign revealed cells wider than your reach stops cargo until a finished Hub reaches across. Waypoints are passage only: a shipment still starts and ends on your own revealed cells. Radius is per cell, never global: a plain cell (Virgin ground included) carries the move radius and each finished Hub tier carries the radius its own catalog row serves, so fromRadius on the origin and radius on every candidate is what you add up. 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. Empty hops means goods can only be hauled up to here. Facts per candidate: hop distance, owner, hub and Virgin flags, ready build state, the exact per-unit transit fee for your resourceId cargo (your own cells charge none, a Hub of your own on them included, and so does bare Virgin ground — but a foreign finished Hub charges its fee even on a cell with no completed reveal), 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. Routing is refused until the whole map has loaded, so a missing row can never pass as open ground. 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. Pass lotId to survey one lot’s way home instead: for an Evicted lot the origin becomes the hub it was listed on, admitted from the lot itself at the reach recorded there, whatever stands on that cell now. Only the origin changes — every candidate is still judged on today’s map — and the chain you build is verified with cpu_quote_lot_return.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesThe cell to hop from — where the cargo stands now: your own cell, a cell with a finished Hub, or Virgin ground (no completed reveal).
lotIdNoOptional lot id — plan the way home for this lot instead of an ordinary shipment. For an Evicted lot the source is the hub it was listed on, admitted from the lot itself with the reach and the rate recorded there, so the plan survives that hub being demolished, rebuilt or sold. Nothing after the source changes: the destination is still your own revealed cell and every waypoint follows the ordinary rules. Verify the chain with cpu_quote_lot_return.
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.

Schema Changelog

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

  1. Changed4 schema fields changedv0.10.0
    • changedInput schema / properties / from / description
      Previous value: -"The cell to hop from (your revealed cell, or a Hub)."New value: +"The cell to hop from — where the cargo stands now: your own cell, a cell with a finished Hub, or Virgin ground (no completed reveal)."
    • changedInput schema / properties / from / maximum
      Previous value: -48990New value: +29150
    • addedInput schema / properties / lotId
      Added value: +{
      +  "anyOf": [
      +    {
      +      "pattern": "^\\d+$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional lot id — plan the way home for this lot instead of an ordinary shipment. For an Evicted lot the source is the hub it was listed on, admitted from the lot itself with the reach and the rate recorded there, so the plan survives that hub being demolished, rebuilt or sold. Nothing after the source changes: the destination is still your own revealed cell and every waypoint follows the ordinary rules. Verify the chain with cpu_quote_lot_return."
      +}
    • changedInput schema / properties / towards / 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.8/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 fully delivers: it discloses read-only behavior, the exact reach formula, unfinished-Hub rules, fee behavior, empty hops semantics, the wall concept, and the requirement that the whole map be loaded. No contradictions with annotations exist because none were provided.

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 it is dense with non-redundant game rules and front-loaded with purpose and eligibility. A few sentences could be tightened, but the structure, including the labeled WHEN section, keeps the content navigable.

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?

Despite having no output schema, the description enumerates the facts returned per candidate, covers edge cases like fromReady and empty hops, and establishes prerequisites such as map loading and caller-owned destinations. For a 4-parameter read-only survey tool, nothing essential appears missing.

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% and the schema already describes parameters well, so baseline is 3. The description adds meaningful nuance beyond that baseline by explaining 'towards' is a compass, not a route, by clarifying lotId changes only the origin, and by spelling out how resourceId drives per-unit fees.

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: 'Survey the legal next waypoints from a cell (read-only)', then explains eligibility and the reach rule in concrete terms. It also distinguishes itself from cpu_route_network and cpu_quote_transport by positioning itself as the cheap point check rather than a planner or verifier.

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 WHEN section is explicit: call before each leg and after cpu_get_changes shows movement, and fall back to cpu_route_network only when a local fix is impossible. It also gives clear alternatives for verification and for the lotId path, including cpu_quote_lot_return.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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