Progressive Discovery

Implement layered MCP discovery with overview, category, and tool detail steps.

3|1|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/standardbeagle/standardbeagle-tools --skill progressive-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Progressive Discovery
Source: https://github.com/standardbeagle/standardbeagle-tools/tree/main/plugins/mcp-architect/skills/progressive-discovery
Command: npx skills add https://github.com/standardbeagle/standardbeagle-tools --skill progressive-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a scalable, guided approach to exposing MCP server capabilities, preventing user overwhelm by progressively revealing tools and documentation.

Core Features & Use Cases

  • Layered discovery with a single entry point (info) that lists categories and counts.
  • Category and tool detail views to drill down into capabilities, usage patterns, and definitions.
  • Example workflows include overview → category → tool details and get_help-like deep dives for full documentation.

Quick Start

Request the info tool to display the overview, then drill into a specific category with info(category="Query Tools"), and finally call get_help("tool_name") for full documentation.

Frequently Asked Questions about Progressive Discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent user overload when exposing an MCP server with many tools?

Prevent MCP user overload by implementing progressive discovery, a pattern that reveals capabilities through layered guidance with a single entry point, category lists, and detailed tool documentation steps.

What is the best way to structure MCP discovery for scalable tool documentation?

Structure MCP discovery using a layered architecture that starts with an overview listing categories and counts, then drills into category-specific tool lists, and finally returns detailed tool documentation.

How do I implement progressive MCP discovery step by step?

Call the info tool for an overview, drill into a specific category using info(category="Query Tools"), and finally call get_help("tool_name") to retrieve full documentation for a specific MCP tool.

Can I use progressive discovery to return structured guidance for MCP servers with extra parameters?

Yes, progressive discovery tolerates extra parameters and returns structured guidance, ensuring the layered info and discovery pattern remains scalable for MCP servers with extensive tool sets.

When should I not use a single entry point for MCP tool discovery?

Avoid a single entry point for MCP discovery if your server exposes only a few tools, as the layered category and detail steps add unnecessary navigation overhead compared to direct tool access.