Skip to main content
Glama
Sign In
maic-server-fs-mcp

maic-server-fs-mcp

by maicFir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

dispatchTask

Assign a specific task to a coder or tester expert, then wait for their results before dispatching the next task.

Instructions

当需要安排下属专家执行具体工作时调用此工具。每次只能派发一个任务，等下属汇报结果后，再派发下一个。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "worker": "<worker>",
      "taskInstruction": "<taskInstruction>"
    },
    "name": "dispatchTask"
  }
}

Input Schema

NameRequiredDescriptionDefault
workerYes接收任务的专家。'CODER' 负责读写代码文件；'TESTER' 负责运行终端编译或测试命令。
taskInstructionYes具体要这个专家执行的详细指令。例如：'帮我查看 src/index.ts 的内容并修复其中的类型 Bug'。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that it dispatches one task and waits for results, but lacks details on side effects, failure handling, or auth requirements.

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?

Two sentences efficiently convey purpose and usage guideline. The description is front-loaded and contains no filler.

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

Completeness3/5

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

The description covers the main workflow but lacks information on return values or what happens after dispatch, which would be helpful given the absence of output schema.

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?

Schema coverage is 100% with clear parameter descriptions. The description adds global workflow context but no additional parameter-specific meaning beyond the schema.

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

Purpose5/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: dispatching a task to a subordinate expert. It distinguishes from siblings like buildCodebaseIndex or writeFile by focusing on delegation.

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

Usage Guidelines4/5

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

The description provides explicit usage context: only one task at a time and wait for results. It does not explicitly mention when not to use it or alternatives, but the sibling tools are distinct.

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

Deploy Server

Other Tools