name: preset-mcp-data description: Use Superset MCP data-returning tools for chart data, chart previews, rendered chart SQL, and dataset query results. Use only for MCP tool workflows; do not use for direct API work.
preset-mcp-data
Use when the user needs data returned through MCP tools.
Always
- Use MCP tools only; do not switch to REST chart-data, SQL Lab, or dataset endpoints.
- Treat returned rows, rendered SQL, chart previews, and dataset query results as potentially sensitive.
- Keep row limits, selected columns, metrics, filters, and formats narrow.
- Use discovery tools first when identifiers, metrics, columns, or chart IDs are unknown.
- Do not use data tools as a workaround after data-model permission denial.
Decision Rules
- Use
get_chart_datafor existing chart result data. - Use
get_chart_previewfor renderable existing chart previews. - Use
get_chart_sqlto inspect rendered chart SQL without executing it. - Use
query_datasetfor semantic-layer metrics, dimensions, filters, and time ranges (saved metrics only; route ad-hoc aggregates topreset-mcp-sqllab). - Route chart creation to
preset-mcp-visualization.
Workflow Order
- Classify which output the request needs: result data, preview content, SQL text, or semantic-layer output. Do not ask the user to re-confirm an explicit data request.
- Resolve the object and schema through discovery if needed.
- Choose
get_chart_data,get_chart_sql,get_chart_preview, orquery_datasetaccording to the requested output. - Request a small result with narrow fields, row limits, and the least revealing format.
- Summarize data carefully; do not paste large raw payloads.
Retrieve
- Data tool routing: references/data-tools.md