tumiki-dynamic-search-feature

Guide implementing, extending, and debugging Dynamic Search on MCP servers.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rayven122/tumiki --skill tumiki-dynamic-search-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tumiki-dynamic-search-feature
Source: https://github.com/rayven122/tumiki/tree/main/.claude/skills/tumiki-dynamic-search-feature
Command: npx skills add https://github.com/rayven122/tumiki --skill tumiki-dynamic-search-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dynamic Searchの実装・拡張・デバッグを促進する包括的な開発ガイド。MCPサーバーのツール発見と実行フローの理解をサポートします。

Core Features & Use Cases

  • Dynamic Searchアーキテクチャの概要とモード(従来モードとDynamic Searchモード)の理解
  • メタツール(search_tools, describe_tools, execute_tool)の追加・統合・デバッグ
  • EE/CE分離アーキテクチャと実装/テスト手順の理解
  • MCPサーバー上のツール検索・実行のデベロッパー向け手順
  • AI検索・ツール実行の統合を加速する実務的ケース

Quick Start

Follow these guidelines to implement, extend, and debug the Dynamic Search feature on the MCP server.

Frequently Asked Questions about tumiki-dynamic-search-feature

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

FAQPage Schema
How do I implement dynamic tool discovery in an MCP server?

Dynamic tool discovery in an MCP server is implemented using meta-tools like search_tools, describe_tools, and execute_tool to enable runtime tool search and execution across proxy and server components.

What is the difference between traditional mode and Dynamic Search mode in MCP?

Dynamic Search mode differs from traditional mode by utilizing meta-tools for tool discovery and runtime execution, whereas traditional mode relies on direct tool exposure without an intermediate search and describe workflow.

How do I add new meta-tools to the MCP server for tool discovery?

Adding new meta-tools to the MCP server involves integrating them into the EE/CE separation architecture, following structured tooling workflows, and testing the tool discovery and execution flows across proxy components.

How does the EE/CE separation architecture affect MCP tool execution?

The EE/CE separation architecture structures MCP tool execution by isolating enterprise and community edition components, ensuring distinct implementation and testing procedures for dynamic search and meta-tool integration.

Why is my MCP dynamic search not finding the expected tools?

MCP dynamic search fails to find expected tools when meta-tools are incorrectly integrated into the proxy or server components, requiring structured debugging of the tool discovery, describe, and execute workflow.

Can I use dynamic search meta-tools to execute tools at runtime across MCP components?

Yes, you can use the execute_tool meta-tool to perform runtime tool execution across MCP proxy and server components after discovering and describing them using search_tools and describe_tools.