Claude Cursor GitHub Copilot Skill

preset-mcp-troubleshooting

Troubleshoot Superset MCP health, validation, permission, response-size, and bug-report workflows. 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-troubleshooting-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-troubleshooting

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

Use when Superset MCP tools fail, return validation errors, return permission errors, or produce oversized responses.

Always

Stay on MCP troubleshooting; do not switch to direct APIs.
Use health_check first for service availability.
Use generate_bug_report when the user says MCP is broken or asks how to report an issue.
Treat permission denied as authoritative.
No permission workaround: do not search alternate tools, REST APIs, or direct APIs to expose restricted data.
Use live tool schemas to fix validation errors.

Decision Rules

Connection or availability issue: health_check.
Tool parameter/schema issue: inspect the live tool schema and retry only with corrected MCP arguments.
Permission issue: explain the denied operation and stop; do not search for alternate tools to expose restricted data.
Response too large: rerun with narrower filters, identifiers, page sizes, or row limits.
Repro/report request: generate_bug_report.

Workflow Order

Classify the failure: availability, validation, permission, unsupported capability, oversized response, or unknown error.
Use the smallest diagnostic MCP tool.
Explain the failure in user terms.
For permission denied, stop or generate bug report when requested.
Stop before direct API or REST API calls.
Retry only when the correction is clear and remains on MCP.

Retrieve

Troubleshooting guide: references/troubleshooting.md

Files (agent-skills)

references

troubleshooting.md 942 B

# Troubleshooting

| Symptom | MCP Action |
|---|---|
| Server availability unclear | Call `health_check` with no arguments. |
| User asks to report an MCP problem | Call `generate_bug_report`. |
| Invalid parameters | Re-read the live tool schema and use the request wrapper if required. |
| Permission denied | Treat permission denied as authoritative. Stop and explain the denied MCP operation. |
| Response too large | Narrow with page size, filters, identifiers, row limits, or a more specific tool. |
| Unsupported chart type/capability | Use supported chart schemas from `get_chart_type_schema` or explain the limitation. |

No permission workaround: do not search alternate tools, REST APIs, or direct APIs to expose restricted data.
For permission denied, stop or generate bug report when requested.
Stop before direct API or REST API calls.

Do not use direct REST/API calls to bypass MCP validation, permissions, or missing tools.

SKILL.md 1.7 KB

---
name: preset-mcp-troubleshooting
description: Troubleshoot Superset MCP health, validation, permission, response-size, and bug-report workflows. Use only for MCP tool workflows; do not use for direct API work.
---

# preset-mcp-troubleshooting

Use when Superset MCP tools fail, return validation errors, return permission errors, or produce oversized responses.

## Always

- Stay on MCP troubleshooting; do not switch to direct APIs.
- Use `health_check` first for service availability.
- Use `generate_bug_report` when the user says MCP is broken or asks how to report an issue.
- Treat permission denied as authoritative.
- No permission workaround: do not search alternate tools, REST APIs, or direct APIs to expose restricted data.
- Use live tool schemas to fix validation errors.

## Decision Rules

- Connection or availability issue: `health_check`.
- Tool parameter/schema issue: inspect the live tool schema and retry only with corrected MCP arguments.
- Permission issue: explain the denied operation and stop; do not search for alternate tools to expose restricted data.
- Response too large: rerun with narrower filters, identifiers, page sizes, or row limits.
- Repro/report request: `generate_bug_report`.

## Workflow Order

1. Classify the failure: availability, validation, permission, unsupported capability, oversized response, or unknown error.
2. Use the smallest diagnostic MCP tool.
3. Explain the failure in user terms.
4. For permission denied, stop or generate bug report when requested.
5. Stop before direct API or REST API calls.
6. Retry only when the correction is clear and remains on MCP.

## Retrieve

- Troubleshooting guide: [references/troubleshooting.md](references/troubleshooting.md)