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 · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download preset-io-agent-skills-plugins_preset-mcp-skills_skills_preset-mcp-discovery-73d2674.zip · 1 KB

preset-io/agent-skills 12 1 forks Apache-2.0 Updated 14d ago

Part of preset-io/agent-skills — 28 skills

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

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

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

Retrieve

Discovery tool map: references/discovery-tools.md

Files (agent-skills)

references

discovery-tools.md 1.5 KB

# Discovery Tools

| Goal | MCP Tool |
|---|---|
| Check service availability | `health_check` |
| Instance overview and counts | `get_instance_info` |
| List charts, dashboards, datasets, databases | `list_charts`, `list_dashboards`, `list_datasets`, `list_databases` |
| Object details | `get_chart_info`, `get_dashboard_info`, `get_dataset_info`, `get_database_info` |
| Valid fields and filters | `get_schema` |
| Chart configuration schema | `get_chart_type_schema` |

Use IDs, UUIDs, or slugs accepted by the live schema. Do not invent identifiers. If a user gives a name, search or list first.

## Discovery Flow

1. Run `health_check` only for MCP service availability, uptime, dependency, or readiness questions.
2. Run `get_instance_info` only for workspace identity, feature, count, or instance overview questions.
3. Use `list_*` before `get_*_info` when the user provides a name instead of an ID; do not repeat an identical list call, but follow pagination or refine the search filter when the target is not in the returned page.
4. Fetch details only for the object needed.
5. When a call fails on filters, sorts, field selections, or request wrappers, fix it against `get_schema` instead of guessing again.
6. Route result-data reads, mutations, and SQL execution to their domain skills; stop before direct API calls.

Discovery tools answer metadata and capability questions. Route returned rows, chart data, previews, rendered SQL, and semantic-layer output to `preset-mcp-data`.

SKILL.md 1.8 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

- 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)