rent.dev

Revoke a node

rent_supply_revoke_node

DestructiveIdempotent

Takes a node out for good: it gets no new leases and its link is removed. A revoked node cannot come back; enrol the machine again for a new node. Revoking a revoked node answers it unchanged. A refusal carries retryable, owner_action_required and next; run next.command after next.after_s seconds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node_id": "<node_id>"
    },
    "name": "rent_supply_revoke_node"
  }
}

Input Schema

Name	Required	Description	Default
`node_id`	Yes	Node id (`n` and 15 characters) from rent_supply_nodes, or from the node kit once a node is claimed.

Output Schema

Name	Required	Description	Default
`id`	Yes
`ask`	Yes
`kit`	No
`next`	Yes
`wire`	Yes
`state`	Yes
`checks`	Yes
`payout`	Yes
`region`	Yes
`reasons`	Yes
`capacity`	Yes
`phase_ms`	Yes
`placement`	Yes
`reachable`	Yes
`templates`	Yes
`endpoint_id`	Yes
`time_to_first_payable_ms`	Yes
`time_to_first_customer_lease_ms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 12, 2026

addedOutput schema / 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 / 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"
+]

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already supply destructiveHint, idempotentHint and openWorldHint, and the description adds real value on top: the concrete effects (leases stop, link removed), irreversibility, and an error contract naming retryable, owner_action_required and next with the next.command/next.after_s retry protocol. It does not discuss permissions or auth required to revoke, which is the remaining gap for a destructive operation.

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?

Four short sentences, front-loaded with the irreversible consequence before the operational details. Every sentence carries distinct information; the final sentence on next.command is terse but functional rather than padded.

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?

A destructive single-parameter tool with an output schema and full annotation coverage; the description covers effects, irreversibility, idempotent behavior and the failure-recovery protocol. Nothing an agent needs in order to call it safely 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?

Only one parameter, node_id, and the schema already documents its format (`n` plus 15 characters) and its origin from rent_supply_nodes or the node kit with 100% coverage. The description adds nothing about the parameter itself, so baseline 3 applies.

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?

States a specific verb and resource ("takes a node out for good") and immediately qualifies the scope with the consequences: no new leases, link removed, permanent. This is unmistakably distinct from sibling operations like rent_supply_update_node or rent_supply_node.

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?

Gives a clear when-to-use criterion (permanent removal) and an implicit when-not-to: if you want the machine back, "enrol the machine again for a new node" points at re-enrollment rather than revocation. It also clarifies the no-op case ("revoking a revoked node answers it unchanged"), removing a common agent hesitation, though it never names a sibling tool explicitly.

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

All rent.dev tools Inspect

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

Need Help?