Draw a chart in the conversation. Use it whenever the answer is a shape rather than a number: a trend over time, a compa
Draw a chart in the conversation. Use it whenever the answer is a shape rather than a number: a trend over time, a comparison across products or campaigns, a split of a total, a relationship between two measures. Prefer a chart to a markdown table for anything with more than about five rows of numbers, and always pass the figures you actually read from a tool — never invent or round data to make a nicer picture. Pick the kind by the question: line/area for a value over time; bar for magnitude across categories; stacked_bar or stacked_area when the TOTAL is also a real quantity; pie or donut for one whole split into a few parts; scatter for two measures against each other; combo for one measure as bars with another as a line. There is no dual-axis chart on purpose — two measures of very different scale go in two charts. ALWAYS set unit (and currency when it is money): a currency drawn as a bare number is a figure the merchant will read as the wrong thing. ALWAYS set source with the tool you read, the window, and the row count, so the merchant can trace the number back. At most 6 series; if you have more, chart the ones that matter and say so. Write a one-line answer in prose as well — the chart supports the sentence, it does not replace it.
Request
- Base URL: https://app.magistry.io
- URL: https://app.magistry.io/api/v1/tools/render_chart
- Auth: one of:
- HTTP bearer
- OAuth 2 (authorization code, authorization URL https://app.magistry.io/api/oauth/authorize, token URL https://app.magistry.io/api/oauth/token, scopes: read)
Request body
Response
Tool result
Changes
No recorded changes to this operation across all 3 revisions of this API.