Skip to main content
Glama
mo666-med

Enhanced Miyabi MCP Server

by mo666-med

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
miyabi__analyze_task_intentC

ユーザーのタスクを分析し、開発関連か一般タスクかを判定します

miyabi__auto_dispatchB

タスクを自動的に適切なハンドラーに振り分けます(開発タスク→Miyabi、一般タスク→Manus)

miyabi__handle_development_taskC

開発タスクを処理します(Issue作成→Agent実行)

miyabi__generate_articleC

医療AI関連の学術記事を生成します(LLMO対策、サムネイル指示付き)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 4 tools

Disambiguation4/5

The tools have distinct primary purposes: analyzing task intent, dispatching tasks, generating articles, and handling development tasks. However, miyabi__auto_dispatch and miyabi__handle_development_task could be slightly confusing as both involve task handling, but their descriptions clarify dispatch vs. execution roles.

Naming Consistency5/5

All tools follow a consistent miyabi__verb_noun pattern with underscores, making them predictable and easy to parse. There are no deviations in naming style across the set.

Tool Count3/5

With 4 tools, the count is reasonable but feels borderline thin for a server named 'Enhanced Miyabi MCP Server' that implies broader functionality. The tools cover specific workflows but may leave gaps in a comprehensive task-handling system.

Completeness3/5

The tools cover key steps like analysis, dispatch, article generation, and development tasks, but there are notable gaps. For example, there's no tool for handling general tasks (Manus) after dispatch, and no update or delete operations for generated articles or tasks, limiting lifecycle coverage.

Maintenance

ActivityInactive
ResponsivenessNo issues