get_dashboard
Read one saved dashboard's current spec — its queries and panels — by name or title. ALWAYS call this before editing one. save_dashboard replaces the whole spec rather than patching it, so an edit built from memory silently drops every panel you did not happen to remember. The response comes back in exactly the shape save_dashboard takes, so an edit is: get it, change the part the user asked about, send it all back. Its last_save is what the save behind this revision found — each query's cost, and any cost_warnings, data_warnings or empty_queries.
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": {
"name": "<name>"
},
"name": "get_dashboard"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Which dashboard, as its name (`sa-wind-vs-price`) or its title ("SA wind vs price"). Both resolve to the same one, so pass whichever the user said. | |
| question_id | No | Optional UUID returned by an earlier `start_question` call. When provided, this tool call is attributed to that question. |