Skip to main content
Glama

tool_swarm

Deploy parallel AI agents with specialized tool permissions to execute complex tasks like system monitoring, code analysis, and file operations through coordinated swarms.

Instructions

Deploy tool-enabled agents that can use real system tools.
Each bug role has different tool permissions:
- scout: read_file, list_dir, file_exists, system_status, process_list
- worker: read_file, write_file, exec_cmd, http_get, http_post
- memory: read_file, kmkb_search, kmkb_ask, list_dir
- guardian: system_status, process_list, disk_usage, check_service
- learner: read_file, analyze_code, list_dir, kmkb_search

tasks: JSON array of task objects:
  Standard: {"prompt": "Do something"}
  Write:    {"path": "/file.txt", "content": "data..."}  <-- DIRECT EXECUTE for long content

Example: [{"prompt": "Check system health"}, {"path": "/tmp/out.txt", "content": "results"}]

DIRECT EXECUTE: Write tasks with content >300 chars bypass LLM entirely.
Bugs can't reliably echo long content - we write directly instead.

deep: Enable deep work mode - bugs chain multiple tool calls for complex tasks
synthesize: If True, uses qwen2.5:14b to synthesize results into unified summary

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYes
colony_typeNohybrid
deepNo
synthesizeNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by explaining key behaviors: role-based tool permissions for different bug roles, the 'DIRECT EXECUTE' mechanism for long content, and how 'deep' and 'synthesize' parameters affect agent behavior. However, it doesn't cover error handling, performance characteristics, or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably structured with clear sections, but contains some redundancy and could be more front-loaded. The bug role permissions list is detailed but necessary, while the 'DIRECT EXECUTE' explanation repeats the content length threshold. Some sentences could be more efficiently phrased to improve conciseness.

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?

Given the tool's complexity (multi-agent deployment with role-based permissions) and the complete lack of annotations and output schema, the description provides substantial context but has gaps. It covers core functionality and parameter behaviors well, but doesn't explain the return format, error conditions, or how results from different agents are organized. The 'colony_type' parameter remains unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate for the lack of parameter documentation. It provides substantial semantic information: it explains 'tasks' with examples and the special 'DIRECT EXECUTE' behavior, clarifies 'deep' enables chaining for complex tasks, and states 'synthesize' uses a specific model for summaries. The only parameter not well-explained is 'colony_type'.

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 tool's purpose: 'Deploy tool-enabled agents that can use real system tools.' It specifies the verb ('deploy') and resource ('tool-enabled agents'), and distinguishes it from siblings by focusing on multi-agent deployment with role-based permissions. However, it doesn't explicitly differentiate from similar swarm tools like 'api_swarm' or 'exec_swarm'.

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?

The description provides some usage context through examples and explanations of parameters like 'deep' and 'synthesize', but lacks explicit guidance on when to use this tool versus alternatives. It mentions 'DIRECT EXECUTE' for specific cases but doesn't compare to sibling tools or outline scenarios where other swarm tools would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BossX429/agent-farm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server