Task Agents
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTS_DIR | Yes | Path to your agents folder. Must be an absolute path (e.g., /Users/john/my-agents on Mac/Linux or C:\Users\john\my-agents on Windows) | |
| AGENT_TYPE | Yes | Which AI tool you're using. Set to 'cursor' for Cursor or 'claude' for Claude Code | |
| EXECUTION_TIMEOUT_MS | No | How long agents can run in milliseconds (default: 5 minutes/300000ms, maximum: 10 minutes/600000ms) | 300000 |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_agentA | Delegate complex, multi-step, or specialized tasks to an autonomous agent for independent execution with dedicated context (e.g., refactoring across multiple files, fixing all test failures, systematic codebase analysis, batch operations). Returns session_id in response metadata - reuse it in subsequent calls to maintain conversation context continuity across multiple agent executions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Agent List | List of available Claude Code sub-agents |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or misselection between tools. The tool's purpose is clearly described and stands alone.
The single tool name 'run_agent' is clear and follows a conventional verb_noun style. There are no other names to contradict a consistent pattern.
A single tool for a server called 'Task Agents' is too few for the apparent scope. Users cannot list, manage, or monitor agents, making the toolset feel extremely thin.
The server provides only an invocation operation with no lifecycle management—no status checks, cancellation, listing, or result retrieval mechanisms. This is severely incomplete for a task-agent-oriented server.