Skip to content

graph_centrality

Structural importance of notes in the persisted link graph. metric ‘pagerank’ answers ‘what do many notes point at’ (power iteration, damping 0.85); metric ‘betweenness’ answers the different question ‘what sits between otherwise disconnected areas’ — a bridge note can score high on betweenness with only two links. ANALYTICS ONLY: these scores are never used for retrieval ranking. Notes outside your read scope are excluded from the graph entirely, not just from the output.

Domain links
Scopes read:notes
Access read
Tags read-only, domain:links, links, graph
Profile full only
Annotation Value
Read-only yes
Destructive no
Idempotent no
Accepts an idempotency key no

Idempotent is the advisory MCP idempotentHint. Destructive is also yes for a tool that asks for confirmation only on some calls.

No human confirmation is required to call this tool.

Parameter Type Required Default Description
vault string — Vault id. May be omitted when only one vault is available. length 1–64; pattern ^[a-z0-9_-]+$
metric enum "pagerank" One of: "pagerank", "betweenness"
min_incoming_links integer 0 range 0–100
limit integer 25 range 1–200
Field Type Always present Description
vault string yes —
metric enum yes One of: "pagerank", "betweenness"
nodes number yes —
available boolean —
message string —
edges number —
results object[] —
results[].path string with parent —
results[].score number with parent —

Other tools in the links domain: find_link_cycles, find_orphans, find_unresolved_links, get_backlinks, get_link_strength, get_outgoing_links, graph_communities, graph_path_between, prune_hub_links, rewrite_link, suggest_links, vault_health_score.

Back to the tool catalog.