Skip to main content
Glama
Sign In
AgentTasker

AgentTasker

by S3bRR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Execute Batch

execute_batch
Destructive

Run independent shell tasks in parallel with dependency ordering, concurrency limits, timeouts, and optional background batches that return a batch ID immediately.

Instructions

Run independent tasks in parallel, including opt-in shell commands. Use depends_on for a plan; concurrency sets the limit, wait=false returns a batch_id immediately.

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": {
      "tasks": "<tasks>"
    },
    "name": "execute_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoFalse returns a background batch_id immediately
tasksYes
concurrencyNo
output_modeNocompact

Output Schema

NameRequiredDescriptionDefault
taskNo
errorNo
statusNo
resultsNo
batch_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, openWorld=true, and non-idempotent behavior, so the safety profile is covered. The description adds meaningful operational context: shell commands are opt-in, concurrency limits execution, depends_on creates a dependency plan, and wait=false returns a batch_id immediately.

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 front-loaded sentence with semicolon-separated clauses, each carrying a distinct operational point. There is no filler or repetition.

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?

This is a complex, destructive, open-world batch shell executor with nested task parameters, and the description covers only the top-level execution model. Annotations and the output schema reduce the burden, but important task-level and output_mode semantics remain unaddressed in the description.

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 low at 25%, so the description must carry more weight. It explains concurrency, wait, and depends_on, but it does not clarify the required tasks structure, task_type enum, output_mode, or task-level fields such as timeout and max_output_bytes.

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 verb and resource: run independent tasks in parallel, with opt-in shell commands. It is specific enough to distinguish a batch executor from single-task execution, but it does not explicitly differentiate itself from siblings such as execute, get_batch, or cancel_batch.

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

Usage Guidelines3/5

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

It gives useful context that this is for independent parallel tasks and notes wait=false for asynchronous batches. However, it does not say when to use this instead of execute, get_batch, or cancel_batch, nor does it state exclusions or prerequisites for safe use.

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