Skip to main content
Glama
shiiman

multi-agent-mcp

by shiiman

send_task

Send a task instruction to an agent via file, specifying task content and session ID, enabling parallel execution in multi-agent environments.

Instructions

タスク指示をファイル経由でエージェントに送信する。※ Owner と Admin のみ使用可能。

Args: agent_id: エージェントID task_content: タスク内容(Markdown形式) session_id: Issue番号または一意なタスクID auto_enhance: 自動拡張を行うか(デフォルト: True) branch_name: 作業ブランチ名(Admin 用、省略時は feature/{session_id}) report_template: レポートテンプレート名(例: "security", "general")。 指定するとテンプレートのファイルパスが Worker のタスク指示に注入される。 caller_agent_id: 呼び出し元エージェントID(必須)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes
session_idYes
branch_nameNo
auto_enhanceNo
task_contentYes
caller_agent_idNo
report_templateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It mentions file-based sending and access restrictions, but it doesn't describe side effects, idempotency, error behavior, or whether the operation is synchronous. The description adds some context but is insufficient for a tool that sends tasks.

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

Conciseness4/5

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

The description is a short paragraph followed by a concise parameter list. It front-loads the main purpose and access constraint. The parameter descriptions are efficient, though the list is relatively long. Overall, it's well-structured without unnecessary text.

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?

Given the tool has 7 parameters and no annotations, the description covers purpose, parameters, and access control. However, it lacks info on prerequisites (e.g., agent must exist), return values (output schema exists but not explained), and differentiation from similar sibling tools. Some gaps remain for full completeness.

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

Parameters4/5

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

The input schema has 0% description coverage, so the description must add meaning. The description provides explanations for all 7 parameters, including examples (e.g., report_template: 'e.g., "security", "general"') and behavior (e.g., injection into Worker's task instructions). This adds significant value beyond schema titles.

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 sends task instructions via file to an agent and specifies access control (only Owner/Admin). It uses a specific verb and resource, which distinguishes it from some siblings like send_command or create_task, but it doesn't explicitly contrast with them.

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 mentions that only Owner and Admin can use the tool, providing a constraint, but it gives no guidance on when to use this tool versus alternatives like enqueue_task, send_command, or create_task. No when-to-use or when-not-to-use information is provided.

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/shiiman/multi-agent-mcp'

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