AgentTasker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_TASKER_MAX_TASKS | No | Maximum number of tasks per batch. Default: 1000. | |
| AGENT_TASKER_MAX_BATCHES | No | Maximum number of retained batches. Default: 32. | |
| AGENT_TASKER_BATCH_TTL_SECONDS | No | Retention time for completed batches in seconds. Default: 3600 (1 hour). | |
| AGENT_TASKER_MAX_PAYLOAD_BYTES | No | Maximum payload size per task in bytes. Default: 1 MB. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| executeB | Run one opt-in shell command on the server host. |
| execute_batchA | 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. |
| get_batchC | Collect background progress and finished results; full mode includes unfinished placeholders. |
| cancel_batchA | Cancel queued tasks and terminate running shell process groups. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: single execution, batch execution, batch retrieval, and batch cancellation. The boundaries between execute and execute_batch are especially clear, and get_batch/cancel_batch cover separate lifecycle operations.
Names use snake_case consistently and mostly follow an action_resource pattern (cancel_batch, execute_batch, get_batch). The single execute tool is a minor deviation but remains intuitive.
Four tools are well-scoped for a task execution service: run single tasks, run batches, inspect batches, and cancel batches. No tool feels redundant or out of place.
The surface covers the core execution lifecycle, including background batch retrieval and cancellation. A list_batches or batch discovery operation is absent, but returned batch_ids from execute_batch mitigate that gap.