Skip to main content
Glama

create_task

Create and assign categorized tasks with requirements and dependencies to agents for automated execution in a repository.

Instructions

Create and assign task to agents with enhanced capabilities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repositoryPathYesAbsolute path to the repository where the task will be created. This determines the context and scope of the task.
taskTypeYesType of task being created (e.g., "feature", "bug", "enhancement", "documentation", "testing"). This helps categorize and prioritize the task.
titleYesShort, descriptive title for the task that summarizes what needs to be done.
descriptionYesDetailed description of the task including requirements, context, and expected outcomes. Should be comprehensive enough for an agent to understand and execute.
requirementsNoOptional object containing specific requirements, configuration, or parameters for the task. Can include priority, estimated duration, assigned agent ID, and other task-specific data.
dependenciesNoOptional array of task IDs that this task depends on. The task will only be eligible for assignment after all dependencies are completed.
Behavior2/5

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

With no annotations present, the description carries the full burden. It does not disclose side effects (e.g., whether creation triggers assignment immediately), permissions needed, or any constraints like rate limits. The term 'enhanced capabilities' is ambiguous.

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

Conciseness4/5

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

The description is a single concise sentence, front-loading the purpose. However, it could be more structured by breaking into a brief usage summary and a note on behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 6 parameters including a nested object and no output schema, the description should at least hint at return values (e.g., task ID) or typical usage flow. It lacks completeness for a moderately complex creation tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the base is 3. The description adds no extra meaning beyond the schema, missing an opportunity to explain relationships between parameters (e.g., how 'requirements' interacts with 'taskType') or provide usage examples.

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 indicates the tool creates and assigns a task to agents, with a mention of 'enhanced capabilities' which is vague but does not obscure the core purpose. It distinguishes from siblings like 'create_execution_plan' which focuses on plans rather than tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'spawn_agent' or 'create_execution_plan'. The description lacks any contextual hints about appropriate scenarios or prerequisites.

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/ZachHandley/ZMCPTools'

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