Get database read-cost
get_read_costAnalyze your app's database read costs over the last days, showing per-user versus overhead totals and a breakdown by operation to identify cost drivers.
Instructions
Get an app's database read-cost over the last days days, split into per-user reads vs un-attributed overhead, plus a breakdown by operation. Per-user attribution works because Crossdeck joins read-cost to the SDK's identity, so you can see which operations drive the bill. Returns the per-user-vs-overhead totals and the by-operation breakdown. Use for 'what's driving our database reads' or 'which operation costs the most'.
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": "get_read_cost"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Look-back window in days (1–90, default 30). | |
| project | No | The app to read, as a project id from list_projects (e.g. 'proj_3a8f137bccdd4f'). With a workspace key (cd_wk_) this is required unless you've set a default via use_project; with a single-app key it is ignored. |