omniseek_graph
Find how entities connect or what is known around a paper, author, or entity by querying a read-only, budgeted evidence graph with typed edges.
Instructions
Use WHEN you want HOW two entities connect, or what OmniSeek already knows AROUND a paper / author / entity; read-only, budgeted projections of its accumulated evidence graph with typed edges (ONE graph).
Tool name: omniseek_graph (your MCP config adds its own prefix; never guess one). Not in your tool list? ToolSearch "omniseek_graph".
Pass view and args (that view's own parameters); a call with no view lists the views and their parameters. Views return node ids, labels and edge tuples, never content. find {label_query, kind?}: the entry point, a name to candidate node ids. stats {}: counts by kind, type and tier. neighborhood {anchor, depth? (<= 2), types?, policy?, max_nodes?}: the subgraph around a node. between {a, b, types?, policy?, max_nodes?}: up to 8 shortest connection paths. voices {doc_ids (<= 64), policy?}: collapse documents to distinct upstream voices. since {anchor, date, types?, max_nodes?}: stored edges added after a date. similar {anchor (a doc), k?}: vector-nearest document candidates, proposals only. policy: conservative (exact-id identity only, default) | working (plus your omniseek_ruling rulings) | exploratory (plus fuzzy candidates). A cut result carries capped: true; a failure returns an error dict. Entity kinds fill in as calls happen, so early emptiness is normal. Record identity with omniseek_ruling, relations with omniseek_statement. More: omniseek docs/TOOLS.md, omniseek_graph.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "omniseek_graph"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| args | No | ||
| view | No |