Skip to content

Agent Mesh

node: drop the gossip and dht_size claims from agent-facing text

Tomas Tormo312ca68640de
diff --git a/agents/skills/agentmesh/SKILL.md b/agents/skills/agentmesh/SKILL.md
index 0f0fa033..916e27a9 100644
--- a/agents/skills/agentmesh/SKILL.md
+++ b/agents/skills/agentmesh/SKILL.md
@@ -117,7 +117,7 @@ A running node serves them under `/debug`, and the `agentmesh-node` CLI wraps ea
endpoint over the node's Unix socket — no token involved:
```bash
-agentmesh-node debug mesh-info # connected peers, DHT size, router peer ID
+agentmesh-node debug mesh-info # connected peers, attached routers, router peer ID
agentmesh-node debug connectivity [peer-id] # ping the Agent Mesh router, or a specific peer
agentmesh-node debug network-info # listen and announced addresses
agentmesh-node debug token-info # local auth token expiration and status
@@ -141,7 +141,7 @@ expired token before restarting or re-enrolling anything.
Start by understanding the local node and mesh state:
-- Use `get_mesh_info` with `{}` to inspect `connected_peers`, `dht_size`, and
+- Use `get_mesh_info` with `{}` to inspect `connected_peers`, `attached_routers`, and
`router_peer_id`.
- Use `list_local_services` with `{}` to see services registered on the local
node.
diff --git a/internal/node/mcp_handlers.go b/internal/node/mcp_handlers.go
index a6495d38..c3d70735 100644
--- a/internal/node/mcp_handlers.go
+++ b/internal/node/mcp_handlers.go
@@ -189,7 +189,7 @@ type FindRemoteToolsParams struct {
Intent string `json:"intent,omitempty" jsonschema:"Natural-language description of what the caller is looking for. Reserved for future semantic ranking; currently accepted but ignored."`
PeerID string `json:"peer_id,omitempty" jsonschema:"Restrict the search to a single peer. Empty means search the whole mesh."`
ServiceName string `json:"service_name,omitempty" jsonschema:"Restrict results to tools whose name starts with this service prefix (e.g. 'code-reviewer'). Empty means no service filter."`
- ToolName string `json:"tool_name,omitempty" jsonschema:"Exact (non-namespaced) tool name to locate across the mesh, e.g. 'review_pr'. Served from gossip announcements when fresh; falls back to a mesh-wide fetch. Empty means list all tools."`
+ ToolName string `json:"tool_name,omitempty" jsonschema:"Exact (non-namespaced) tool name to locate across the mesh, e.g. 'review_pr'. Empty means list all tools."`
}
// remoteToolRow is one entry in the find_remote_tools response.
diff --git a/site/content/docs/reference/node-api.md b/site/content/docs/reference/node-api.md
index 898bfd86..e9278b81 100644
--- a/site/content/docs/reference/node-api.md
+++ b/site/content/docs/reference/node-api.md
@@ -181,7 +181,7 @@ called over HTTP and not with `call_remote_tool`.
|---|---|
| `peer_id` | Restrict the search to one peer. |
| `service_name` | Restrict the search to one service, bare (`code-reviewer`) or namespaced (`mcp://code-reviewer`). |
-| `tool_name` | Exact tool name to locate across the mesh (`review_pr`). Answered from gossip announcements when they are fresh. |
+| `tool_name` | Exact tool name to locate across the mesh (`review_pr`). |
| `intent` | Accepted and ignored. Reserved for later use. |
Returns one row per tool with `peer_id`, `tool_name` (namespaced as