route_intent
Maps an analytical intent to recommended warehouse tables to use and avoid, helping AI agents select correct tables for business queries.
Instructions
Which tables to use (and avoid) for an analytical intent.
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": {
"intent": "<intent>"
},
"name": "route_intent"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| intent | Yes | What the user wants to measure, in a few plain words, such as 'monthly revenue by region'. Matched by word overlap against the layer's routing entries, and the five closest come back. Each names the tables to `use`; an `aggregates` list holds summary tables that are offered with a caveat and are not for automatic use. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |