Read a remote node's hardware board
get_node_boardRetrieve the hardware board or model identifier of a remote repeater node.
Instructions
Read a remote repeater's hardware board / model identifier. Equivalent to admin <node> board. Required node. For the home node, use get_node_health() (the firmware.manufacturerModel field) — that's the structured equivalent via the companion protocol, no admin call needed.
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": "<node>"
},
"name": "get_node_board"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| node | Yes | target node (contact name or hex public-key prefix); required (this command isn't implemented on companion firmware so it can't target home) | |
| dryRun | No | preview the intent without contacting the device |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| command | Yes | ||
| tier | Yes | ||
| annotations | Yes | the deterministic per-command risk hints this tier maps to; surfaced here (not as MCP tool-level annotations) because `admin` is one multiplexed tool | |
| dryRun | Yes | ||
| via | No | ||
| preview | No | ||
| reply | No |