Skip to main content
Glama

Change a node

rent_supply_update_node
Idempotent

Changes a node's ask, capacity, region or payout. A new ask applies to leases placed from now on; running leases keep their rates. More slots or a new region sends the node back to probing. payout is the USDC address this node is paid to from the next payout on; the node view shows it as payout, null while none is registered. Change it only when the user asks, with the address the user gave. Each node is paid once a day, in USDC, to the address registered on that node; a node without an address is not paid and its releasable earnings wait until one is registered. A payout cannot be reversed, and a payout made is never sent again to another address. Changing payout needs signed_nonce: a nonce from GET /v1/accounts/nonce, signed with your account's agent key over the message rent.dev payout v2\n<node_id>\n<nonce>\n<public_key>\n<network>\n<address> (six lines joined by newlines, no newline at the end). <address> is payout.address in lowercase. <network> is payout.network when you send it, else the payout network: payouts.network in rent_supply_earnings (while that is null, send payout.network and sign over it). Sign over exactly the address and network you send; a proof for another node, address or network is refused with payout_proof_required, and so is the old four-line message. 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_update_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
askNoUSD per vCPU-hour and per GiB-hour, as decimal strings.
payoutNoWhere this node's payouts go. Each node is paid once a day, in USDC, to the address registered on that node; a node without an address is not paid and its releasable earnings wait until one is registered. A payout cannot be reversed, and a payout made is never sent again to another address.
regionNoA generic label such as `us-central`.
node_idYesNode id (`n` and 15 characters) from rent_supply_nodes, or from the node kit once a node is claimed.
capacityNo
signed_nonceNoRequired with `payout`.

Output Schema

NameRequiredDescriptionDefault
idYes
askYes
kitNo
nextYes
wireYes
stateYes
checksYes
payoutYes
regionYes
reasonsYes
capacityYes
phase_msYes
placementYes
reachableYes
templatesYes
endpoint_idYes
time_to_first_payable_msYes
time_to_first_customer_lease_msYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / payout / additionalProperties
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / payout / description
      Added value: +"Where this node's payouts go. Each node is paid once a day, in USDC, to the address registered on that node; a node without an address is not paid and its releasable earnings wait until one is registered. A payout cannot be reversed, and a payout made is never sent again to another address."
    • addedInput schema / properties / payout / properties
      Added value: +{
      +  "address": {
      +    "description": "The USDC address payouts go to: 0x and 40 hex digits, lowercase or with a correct EIP-55 checksum, never the zero address.",
      +    "type": "string"
      +  },
      +  "network": {
      +    "description": "CAIP-2 network of the address, e.g. `eip155:8453`. Leave it out for the payout network; any other is refused.",
      +    "type": "string"
      +  }
      +}
    • removedInput schema / properties / payout / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / payout / required
      Added value: +[
      +  "address"
      +]
    • 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"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) the description discloses real side effects: a new ask only affects future leases, added slots or a new region re-enters probing, payout edits are irreversible and never re-sent elsewhere. It also documents the refusal path (`payout_proof_required`), the retryable/owner_action_required/next fields, and the exact signing requirements for `signed_nonce`.

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 purpose and the highest-risk field (payout) are front-loaded, and each sentence about signing or refusals carries non-redundant information. It loses a point because the three-sentence block about daily USDC payouts and irreversibility is repeated nearly verbatim from the schema's `payout` property description.

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?

For a multi-field mutation with nested objects and an output schema, the description covers everything an agent must know to call it correctly: credit semantics, probing side effects, signing construction, and the shape of a refusal with its retry instruction. Nothing essential is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 83%, yet the description still adds substantial meaning: the six-line canonical message for `signed_nonce`, that `<address>` must be lowercase `payout.address`, how `<network>` resolves against `payouts.network` in rent_supply_earnings, and that a proof for another node/address/network or the old four-line message is refused.

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?

The opening sentence names a specific verb and resource plus the exact fields touched (ask, capacity, region, payout), so an agent can tell this apart from probe/revoke siblings without opening the schema. It does not explicitly name a sibling it replaces, which keeps it from a 5.

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?

Guidance is concrete where it matters: payout should be changed 'only when the user asks, with the address the user gave', and the description states which changes trigger a return to probing. It gives clear context but never explicitly contrasts with alternatives such as rent_supply_probe_node or rent_supply_revoke_node.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources