Skip to main content
Glama
mo666-med

Enhanced Miyabi MCP Server

by mo666-med

miyabi__analyze_task_intent

Analyzes user prompts to classify tasks as development-related or general, enabling appropriate routing for processing.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYes分析するユーザーのプロンプト

Implementation Reference

  • The core handler function for the 'miyabi__analyze_task_intent' tool. It uses helper functions to classify the input prompt as development, article writing, or general task and returns a JSON-structured response.
    case "miyabi__analyze_task_intent": {
      const isDev = isDevelopmentTask(args.prompt);
      const isArticle = isArticleWritingTask(args.prompt);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            isDevelopmentTask: isDev,
            isArticleWritingTask: isArticle,
            taskType: isArticle ? "article" : (isDev ? "development" : "general"),
            prompt: args.prompt
          }, null, 2)
        }]
      };
    }
  • Input schema defining the expected parameters for the tool: a 'prompt' string.
    inputSchema: {
      type: "object",
      properties: {
        prompt: {
          type: "string",
          description: "分析するユーザーのプロンプト"
        }
      },
      required: ["prompt"]
    }
  • src/handlers.js:47-60 (registration)
    Tool registration within the listToolsHandler function, defining name, description, and input schema.
    {
      name: "miyabi__analyze_task_intent",
      description: "ユーザーのタスクを分析し、開発関連か一般タスクかを判定します",
      inputSchema: {
        type: "object",
        properties: {
          prompt: {
            type: "string",
            description: "分析するユーザーのプロンプト"
          }
        },
        required: ["prompt"]
      }
    },
  • Helper function to detect if the prompt is related to development tasks by checking for specific keywords.
    export function isDevelopmentTask(prompt) {
      const devKeywords = [
        'コード', 'プログラム', 'バグ', 'デバッグ', 'テスト', 'デプロイ',
        'API', 'データベース', 'フロントエンド', 'バックエンド', 'リファクタリング',
        '実装', '開発', 'アプリ', 'ウェブサイト', 'システム', 'モジュール',
        'code', 'program', 'bug', 'debug', 'test', 'deploy',
        'api', 'database', 'frontend', 'backend', 'refactor',
        'implement', 'develop', 'app', 'website', 'system', 'module'
      ];
    
      const lowerPrompt = prompt.toLowerCase();
      return devKeywords.some(keyword => lowerPrompt.includes(keyword.toLowerCase()));
    }
  • Helper function to detect if the prompt is related to article writing tasks by checking for specific keywords.
    export function isArticleWritingTask(prompt) {
      const articleKeywords = [
        '記事', '論文', 'note', 'ブログ', '執筆', '書いて', '作成',
        'article', 'paper', 'blog', 'write', 'create', 'post',
        '医療AI', '医療', 'AI', 'LLMO', 'サムネイル', 'ハッシュタグ'
      ];
    
      const lowerPrompt = prompt.toLowerCase();
      return articleKeywords.some(keyword => lowerPrompt.includes(keyword.toLowerCase()));
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool analyzes and classifies tasks but doesn't describe how it behaves—e.g., whether it's read-only, if it has rate limits, what permissions are needed, or what the output format looks like. This leaves significant gaps in understanding the tool's operational traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for its function, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the analysis returns (e.g., classification results or confidence scores), behavioral aspects like error handling, or how it integrates with sibling tools. For a tool with no structured metadata, more contextual detail is needed to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'prompt' parameter fully documented. The description doesn't add any extra meaning beyond the schema, such as examples or format details, but since the schema does the heavy lifting, the baseline score of 3 is appropriate for adequate parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'analyze user tasks and determine whether they are development-related or general tasks.' It uses specific verbs ('analyze,' 'determine') and identifies the resource ('user tasks'). However, it doesn't explicitly differentiate from sibling tools like 'miyabi__auto_dispatch' or 'miyabi__handle_development_task,' which might have overlapping functions, so it doesn't reach the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, exclusions, or compare it to sibling tools such as 'miyabi__auto_dispatch' or 'miyabi__handle_development_task,' leaving the agent to infer usage context without explicit direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mo666-med/enhanced-miyabi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server