Walk the Graph
pointrover_graphReturns many connected pieces at once, such as what the business buys and what is upstream of it, its wages, rules and locations, and how each links to the next. Use this when the assistant is weighing many things together, such as everything moving against the business beyond its usual range. Not for the business's own books: invoices, bank, payroll or accounting live in its accounting connector, not here. Nor is it search: this walks many items and their connections, at more cost; one item is cheaper through search and fetch. Each item comes with its figure, how unusual its move is, which way it cuts, and whether it is preliminary, corrected or withheld. Pass start (string id; default the business), edges (array of edge kinds), depth (integer 1 to 3, default 1), where (up to 4 filters, OR between them, AND within), detail (concise or full) and token_budget (integer). Example: pointrover_graph({"depth": 2, "where": [{"band_at_least": "unusual", "direction": "against"}, {"kind": ["event"], "state": ["open"]}]}). About 3000 tokens by default and up to 12000; anything trimmed is stated. County demand readings and what they support are described in the docs.
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": "pointrover_graph"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| depth | No | How many edges out to walk. Default 1, capped at 3. | |
| edges | No | Which edge kinds to follow; only these are served. Omit to follow this business's own edges, the industry's typical items left out and counted. The vocabulary is the read model's own: supplies and consumes are stored arcs; the rest are the fixed verbs the board already draws for each collection. | |
| start | No | The record id to walk from, as search, fetch or pointrover_brief returns them. Defaults to this business's own node. The company handle from any answer is accepted here too. | |
| where | No | Filters over states this contract already serves. Fields inside ONE filter are joined by AND; the list is joined by OR, which is how one call asks about records of several shapes at once. Every field is optional. A single filter object is accepted here as well as a list of one. | |
| detail | No | concise is the default and gives each node its identity, figure and states. full adds each node's whole record, which buys fewer nodes for the same budget. | |
| token_budget | No | Estimated-token ceiling for the answer. Default 3000. |