← PresetCONTENT HISTORY
WHAT CHANGED
Update to Preset
Snapshot Oct 24, 2026 · 13:46 UTC · version 0.1.4
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Preset and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot 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.",
"included_files": [
{
"relative_path": "references/data-tools.md",
"size_in_bytes": 1615
}
],
"name": "preset-mcp-data",
"skill_md_contents": "---\nname: preset-mcp-data\ndescription: 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.\n---\n\n# preset-mcp-data\n\nUse when the user needs data returned through MCP tools.\n\n## Always\n\n- Use MCP tools only; do not switch to REST chart-data, SQL Lab, or dataset endpoints.\n- Treat returned rows, rendered SQL, chart previews, and dataset query results as potentially sensitive.\n- Keep row limits, selected columns, metrics, filters, and formats narrow.\n- Use discovery tools first when identifiers, metrics, columns, or chart IDs are unknown.\n- Do not use data tools as a workaround after data-model permission denial.\n\n## Decision Rules\n\n- Use `get_chart_data` for existing chart result data.\n- Use `get_chart_preview` for renderable existing chart previews.\n- Use `get_chart_sql` to inspect rendered chart SQL without executing it.\n- Use `query_dataset` for semantic-layer metrics, dimensions, filters, and time ranges (saved metrics only; route ad-hoc aggregates to `preset-mcp-sqllab`).\n- Route chart creation to `preset-mcp-visualization`.\n\n## Workflow Order\n\n1. 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.\n2. Resolve the object and schema through discovery if needed.\n3. Choose `get_chart_data`, `get_chart_sql`, `get_chart_preview`, or `query_dataset` according to the requested output.\n4. Request a small result with narrow fields, row limits, and the least revealing format.\n5. Summarize data carefully; do not paste large raw payloads.\n\n## Retrieve\n\n- Data tool routing: [references/data-tools.md](references/data-tools.md)\n"
}SHA-256 of public snapshot: 500da54f8e07acdfebdc28ea2bfd00de08be66fd9d01a04801024faac3c53b28