Custom view vocabulary: sources, fields, formats and chart types
list_view_sourcesThe schema for custom views: every data source a view can read, each source's fields (dimensions and measures, with what they mean), the column formats, the render types (table, bar, pie, line, kpi), the ranges and the caps, plus the exact spec shape and its rules. Call this BEFORE writing a spec for preview_view or manage_view; a spec can only name what this lists, and anything else is refused with the path of the problem. available_sources is what THIS account can use. Takes no arguments.
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": "list_view_sources"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| caps | No | Limits: columns, filters, sort keys, name length, spec size. | |
| error | No | Present ONLY when the call was refused instead of answered: upgrade_required (Pro plan needed), not_found, profile_not_found, profile_ambiguous, invalid_arguments, write_not_permitted, rate_limited, limit_reached, view_unavailable. No data fields come with it; read `message` to the user rather than retrying the same call. | |
| guide | No | The full vocabulary and rules, written for a model: the spec shape, every source and field, and an example. | |
| ranges | No | Range values a spec may name. | |
| message | No | Plain-language explanation that accompanies `error`, `data_status` or a proposed change. Read it to the user. | |
| profile | No | The portfolio these figures belong to (absent on list_profiles). | |
| version | No | The spec version, the `v` every spec carries. | |
| next_step | No | What the user should do about data_status. | |
| source_url | No | Link to the page in the WhereItGoes app that shows this data. | |
| data_status | No | Present only when the portfolio has no data yet. nothing_connected: no exchange and no wallet is connected, so empty lists and zeros mean "no data", NOT a $0 portfolio, and no data fields come with it (except on get_connections, get_alerts, get_target_allocation and list_profiles, which also answer). Send the user to next_step. syncing: a source is connected but its first sync is still running, so figures are partial and not final. | |
| upgrade_url | No | Where the user can upgrade, on an upgrade_required refusal. | |
| render_types | No | Chart types a spec may name. | |
| stock_assets | No | Present when the answer mentions Binance Stocks shares (EQ_<ticker>): they are US stocks, not crypto. | |
| available_sources | No | Source keys THIS account can use. |