Find connection between nodes
find_graph_connectionExplain HOW two things in the archive are related: the shortest chain of relationships between any two nodes — two recipes (shared cookbook? shared ingredient?), a person and a recipe, an appliance and an author. Returns the labeled path or reports they're unconnected. Node ids are ':' — e.g. 'entry:' (prefix a search_recipes hit id with 'entry:'), 'ingredient:brown-sugar', 'author:mother-in-law', 'appliance:oven', 'user:'. User-supplied metadata is traversable too: 'tag:' (a shared free-form label) and 'property::' (a shared key=value, e.g. 'property:region:alaska') — every entry carrying that tag/value links to the same node. Recipes with named sub-preparations carry 'component::' nodes (HAS_COMPONENT from the entry; the component links to its own ingredients/steps) — e.g. "what else uses this sauce?" is one hop.
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": {
"from": "<from>",
"to": "<to>"
},
"name": "find_graph_connection"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Second node id (bare recipe ids auto-resolve). | |
| from | Yes | First node id (bare recipe ids auto-resolve). | |
| edge_types | No | Restrict the path to these relationship types. |