← 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 health, instance, list, detail, schema, and chart-type discovery tools. Use only for MCP tool workflows; do not use for direct API work.",
"included_files": [
{
"relative_path": "references/discovery-tools.md",
"size_in_bytes": 1497
}
],
"name": "preset-mcp-discovery",
"skill_md_contents": "---\nname: preset-mcp-discovery\ndescription: Use Superset MCP health, instance, list, detail, schema, and chart-type discovery tools. Use only for MCP tool workflows; do not use for direct API work.\n---\n\n# preset-mcp-discovery\n\nUse for MCP metadata discovery that does not require result data or persistent changes.\n\n## Always\n\n- Use the single narrowest tool that answers the question; discovery calls are for missing IDs, names, or schemas — not a mandatory ladder.\n- Do not repeat an identical list call; reuse earlier results. Following pagination or refining a search filter when the target was not in the returned page is fine.\n- When a call fails on filter, sort, pagination, or request wrapper fields, fix it against the live tool schema rather than guessing again.\n- Do not expose hidden dataset, database, schema, or SQL details after permission errors.\n\n## Decision Rules\n\n- Use `health_check` and `get_instance_info` only when the user asks about service health or the workspace itself.\n- Use `list_*` tools once to find IDs when the identifier is missing; pick a `page_size` that covers the request in one call.\n- Use `get_*_info` for details of a specific known object.\n- Use `get_schema` only when a request fails or valid filter/sort/select fields are genuinely unknown.\n\n## Workflow Order\n\n1. If the needed ID, UUID, slug, or other schema-accepted identifier is already known, skip listing and act on it. Resolve a bare display name with one list/search call.\n2. Otherwise list/search once for the object type in question.\n3. Fetch details only for the specific object needed.\n4. Route to `preset-mcp-data` for result rows, chart data, previews, or rendered SQL.\n5. Route to mutation-focused skills before creating or updating objects.\n\n## Retrieve\n\n- Discovery tool map: [references/discovery-tools.md](references/discovery-tools.md)\n"
}SHA-256 of public snapshot: 230f0b849530df742be4ca36c78eeccfe63fe0dba00adead77fa5d63f1eca97b