Skip to main content
Glama
Sign In
Agent-Comm-Hub

Agent-Comm-Hub

by liuboacean
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_parallel_group

Create a parallel group to execute multiple independent tasks simultaneously, reducing wait time by allowing tasks to run concurrently.

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": {
      "task_ids": "<task_ids>"
    },
    "name": "create_parallel_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idsYes并行任务 ID 列表（至少 2 个，最多 10 个）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.6

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided. The description states the core behavior (simultaneous execution) but lacks details on side effects, reversibility, permissions, or response. For a mutation tool, this is insufficient.

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, front-loaded with the action and purpose. Every word earns its place with no redundancy.

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

Completeness4/5

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

Given one parameter, no output schema, and no annotations, the description is fairly complete. It covers purpose, usage context, and parameter constraints are in schema. However, it omits reversibility and response behavior.

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 description coverage is 100% and the description adds no significant meaning beyond what the schema already provides. Baseline 3 applies.

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 verb 'mark' and resource 'parallel group', and explains that tasks can execute simultaneously. It distinguishes from sibling tools like add_dependency by focusing on parallel execution.

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?

Explicitly states '适用于无依赖关系的同层任务' (suitable for tasks at the same level with no dependencies), providing clear context. Does not name alternatives but the sibling list implies add_dependency is the alternative for dependencies.

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