ClaudeArmy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dispatch_taskA | Deploy a Claude Code agent to work on a task in a specific project directory. The agent runs autonomously with full Claude Code capabilities including sub-agent spawning, file editing, bash execution, etc. Use this to delegate coding tasks to background agents. IMPORTANT: After dispatching, return to the conversation immediately. Do NOT call check_tasks or get_task_output unless the user explicitly asks for a status update. |
| check_tasksA | Check the status of all deployed Claude Code agents. Shows which tasks are running, completed, or failed. Use this to monitor progress of background agents. |
| get_task_outputA | Retrieve the full output from a Claude Code agent task. Use this to see what the agent did, including its reasoning and actions taken. |
| cancel_taskA | Cancel a running Claude Code agent task. Sends SIGTERM to gracefully stop the agent. |
| purge_tasksA | Clear completed/failed tasks from the task list. Optionally clear all tasks (cancels running ones). |
| get_agent_teamA | Get a detailed view of a lead agent and all sub-agents it has spawned. Use this when a task is using Claude Code agent teams to see the full picture of what each sub-agent is doing, their status, and output previews. More detailed than check_tasks for multi-agent operations. |
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 6 tools
The tools are mostly distinct: dispatch_task creates, check_tasks monitors overall status, get_task_output retrieves output, cancel_task stops, purge_tasks cleans up, and get_agent_team drills into team hierarchy. However, check_tasks and get_agent_team both report status, with get_agent_team being more detailed, so there is minor potential for misselection.
All tool names follow a consistent verb_noun pattern with underscores, such as check_tasks, get_task_output, and dispatch_task. The verbs are clear and related to task management, and the minor pluralization difference (task vs tasks) does not affect readability.
Six tools is well within the ideal range for a focused task-management server. Each tool corresponds to a distinct action in the agent lifecycle—dispatch, monitor, retrieve, cancel, purge, and team inspection—so none feel redundant or missing.
The server covers the core lifecycle of Claude Code agents: creation (dispatch_task), status monitoring (check_tasks, get_agent_team), output retrieval (get_task_output), cancellation (cancel_task), and cleanup (purge_tasks). Minor gaps include no explicit retry or update mechanism, and get_agent_team only applies to team-based tasks, but the primary workflows are covered.