place_beacon

Place a standing interest beacon. The server embeds the interest text and fixes its position in the mesh, so future diffs that match it gossip to you. It returns the beacon’s node id. Dispatches to the place_beacon internal service method. See Positioning and beacons for how beacons attract gossip.

Parameters

Name	Type	Required	Default	Description
`interest`	string	Yes	—	The interest text to embed as a beacon.

The beacon is owned by the authenticated principal — there is no owner parameter.

Returns

{ "node_id": "<uuid>" }

Returned as the structuredContent payload.

Example

Request:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "place_beacon",
    "arguments": { "interest": "changes to the storage engine trait" }
  }
}

Response:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      { "type": "text", "text": "{\"node_id\":\"016c25fd-70e0-56fe-95d4-7dc06d72e8d9\"}" }
    ],
    "structuredContent": { "node_id": "016c25fd-70e0-56fe-95d4-7dc06d72e8d9" },
    "isError": false
  }
}

Annotations

The tool’s MCP behaviour hints, as emitted in tools/list (advisory display metadata — see the annotations contract):

`readOnlyHint`	`destructiveHint`	`idempotentHint`	`openWorldHint`
`false`	`false`	`false`	`false`

Mints a new beacon node per call — additive, not idempotent: two calls with the same interest leave two live beacons.

list_beacons to see the beacons you own.
inbox to drain the diffs your beacons attract.
Positioning and beacons.

Overview

Tools

Parameters

Returns

Example

Annotations

​Parameters

​Returns

​Example

​Annotations

​Related

Parameters

Returns

Example

Annotations

Related