Skip to main content
Glama
Sign In

rent.dev

by dev.rent
OverviewDiscussionsAdmin

List your nodes

rent_supply_nodes
Read-onlyIdempotent

Your nodes, newest claim first, each with its state, checks and next step. next_cursor is only for the next call of this tool.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rent_supply_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1-200. Default 50.
cursorNo

Output Schema

NameRequiredDescriptionDefault
dataYes
next_cursorYesPass back as `cursor` for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / data / items / properties / payout
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "address": {
+          "pattern": "^0x[0-9a-f]{40}$",
+          "type": "string"
+        },
+        "network": {
+          "anyOf": [
+            {
+              "pattern": "^eip155:[1-9][0-9]*$",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "address",
+        "network"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / data / items / required
      Previous value: -[
-  "id",
-  "endpoint_id",
-  "state",
-  "wire",
-  "region",
-  "ask",
-  "capacity",
-  "templates",
-  "checks",
-  "reasons",
-  "reachable",
-  "next",
-  "phase_ms",
-  "placement",
-  "time_to_first_payable_ms",
-  "time_to_first_customer_lease_ms"
-]New value: +[
+  "id",
+  "endpoint_id",
+  "state",
+  "wire",
+  "region",
+  "ask",
+  "capacity",
+  "templates",
+  "checks",
+  "reasons",
+  "reachable",
+  "next",
+  "phase_ms",
+  "placement",
+  "time_to_first_payable_ms",
+  "time_to_first_customer_lease_ms",
+  "payout"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real context beyond that: result ordering, the fields carried per node, and the constraint that a returned `next_cursor` is scoped to this tool only. It still does not disclose whether pagination terminates with a null cursor or how large the underlying set typically is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler. The resource and its ordering lead, and the cursor-scoping rule follows as the one non-obvious caveat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not enumerate return fields, and it does enough by naming the ordering and the cursor rule. What is missing is prerequisite context (must the caller be an enrolled supplier?) and pagination termination behavior.

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 50%: `limit` is documented in the schema, while `cursor` is not. The description partly compensates by explaining the cursor's provenance and that it is only valid for the next call of this tool, but it uses the returned field name `next_cursor` rather than the parameter name `cursor`, leaving a small mapping ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource with scope ("Your nodes") and adds ordering ("newest claim first") plus the per-item shape (state, checks, `next` step). It is distinguishable from the singular `rent_supply_node`, but it does not explicitly name that sibling or contrast the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: it lists nodes you have claimed, which suggests the caller should already have supply enrolled. There is no explicit statement of when to use this instead of `rent_supply_node` or `rent_supply_probe_node`, nor any when-not condition or prerequisite.

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

All rent.dev toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources