Skip to main content
Glama
S3bRR

AgentTasker MCP Server

by S3bRR

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENT_TASKER_MAX_TASKSNoMaximum tasks per execute_batch
AGENT_TASKER_MAX_MEMORY_MBNoSoft process memory guard
AGENT_TASKER_MAX_PAYLOAD_BYTESNoMaximum payload size per task

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
executeB

Run one task and return its result.

execute_batchA

Run many tasks in parallel and return ordered results.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one executes a single task, the other executes multiple tasks in parallel. There is no overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern: 'execute' and 'execute_batch'. The batch suffix clearly indicates the parallel execution variant.

Tool Count3/5

With only 2 tools, the server feels minimal. While it covers the basic task execution needs, the scope of a 'Tasker' service might warrant additional tools for management (e.g., listing, canceling). The count is borderline but acceptable for a narrow focus.

Completeness2/5

The server lacks tools for task management beyond execution, such as listing tasks, checking status, canceling, or deleting. This creates significant gaps for an agent needing full task lifecycle support.

Maintenance

ActivityInactive
ResponsivenessNo issues