Claude Cursor GitHub Copilot Skill

preset-mcp-discovery

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.

LLM Mart · 0 points · 3 views 0 listing impressions 0 install-command copies
Download preset-io-agent-skills-plugins_preset-mcp-skills_skills_preset-mcp-discovery-838f0a4.zip · 1 KB

Install

skills CLI npx skills add https://github.com/preset-io/agent-skills/tree/master/plugins/preset-mcp-skills/skills/preset-mcp-discovery
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install preset-io-agent-skills@llmmart
Git git clone https://github.com/preset-io/agent-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole preset-io/agent-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

preset-mcp-discovery

Use for MCP metadata discovery that does not require result data or persistent changes.

Always

  • On the Preset gateway, start with preset-mcp-gateway (list_workspaces, workspace selection). The list/detail tools below are workspace tools called through call_tool.
  • Use the single narrowest tool that answers the question; discovery calls are for missing IDs, names, or schemas — not a mandatory ladder.
  • 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.
  • When a call fails on filter, sort, pagination, or request wrapper fields, fix it against the live tool schema rather than guessing again.
  • Do not expose hidden dataset, database, schema, or SQL details after permission errors.

Decision Rules

  • Use health_check and get_instance_info only when the user asks about service health or the workspace itself.
  • Use list_* tools once to find IDs when the identifier is missing; pick a page_size that covers the request in one call.
  • Use get_*_info for details of a specific known object.
  • Use get_schema only when a request fails or valid filter/sort/select fields are genuinely unknown.

Workflow Order

  1. 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.
  2. Otherwise list/search once for the object type in question.
  3. Fetch details only for the specific object needed.
  4. Route to preset-mcp-data for result rows, chart data, previews, or rendered SQL.
  5. Route to mutation-focused skills before creating or updating objects.

Retrieve

Files (agent-skills)
  • references
    • discovery-tools.md 1.5 KB
      Loading…
  • SKILL.md 2 KB
    ---
    name: preset-mcp-discovery
    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.
    ---
    
    # preset-mcp-discovery
    
    Use for MCP metadata discovery that does not require result data or persistent changes.
    
    ## Always
    
    - On the Preset gateway, start with `preset-mcp-gateway` (`list_workspaces`, workspace selection). The list/detail tools below are workspace tools called through `call_tool`.
    - Use the single narrowest tool that answers the question; discovery calls are for missing IDs, names, or schemas — not a mandatory ladder.
    - 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.
    - When a call fails on filter, sort, pagination, or request wrapper fields, fix it against the live tool schema rather than guessing again.
    - Do not expose hidden dataset, database, schema, or SQL details after permission errors.
    
    ## Decision Rules
    
    - Use `health_check` and `get_instance_info` only when the user asks about service health or the workspace itself.
    - Use `list_*` tools once to find IDs when the identifier is missing; pick a `page_size` that covers the request in one call.
    - Use `get_*_info` for details of a specific known object.
    - Use `get_schema` only when a request fails or valid filter/sort/select fields are genuinely unknown.
    
    ## Workflow Order
    
    1. 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.
    2. Otherwise list/search once for the object type in question.
    3. Fetch details only for the specific object needed.
    4. Route to `preset-mcp-data` for result rows, chart data, previews, or rendered SQL.
    5. Route to mutation-focused skills before creating or updating objects.
    
    ## Retrieve
    
    - Discovery tool map: [references/discovery-tools.md](references/discovery-tools.md)
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.