Skip to main content
Glama

create_task

Create a new task in the event-sourced task graph for multi-agent orchestration. Add work items before assigning them to agents.

Instructions

Create a new task in the event-sourced task graph for multi-agent orchestration.

Use this to add work items before assigning them to agents. For updating an existing task's priority, use change_task_priority instead. This appends a TASK_CREATED event to the append-only SQLite event log with stable UUIDv7 ordering.

Side effects: Creates a TASK_CREATED event in the project's event log. Triggers an automatic snapshot when the event threshold is reached. Does NOT assign the task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYesRequired task objective (1-3 sentences recommended). Should describe what needs to be accomplished, not how.
kindNoTask category (default "implementation"). Common values: "implementation", "review", "testing", "research", "design".implementation
task_idNoOptional explicit task ID; if omitted, a stable UUIDv7 is auto-generated.
priorityNoImportance level from 1 (low) to 5 (critical); higher priority tasks are scheduled first by the deterministic scheduler. Default 3.
related_filesNoOptional list of file paths this task touches; helps agents provide relevant context and reduces hallucination risk.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description carries full burden. It discloses side effects: creates TASK_CREATED event, triggers automatic snapshot, does not assign task. Also describes event-sourced nature and ordering.

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

Conciseness5/5

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

Three sentences, each serving a distinct purpose: purpose, usage, side effects. No redundant content.

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

Completeness5/5

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

Given output schema exists, description covers essential behavioral and usage context for a 5-parameter tool. Side effects and usage boundaries are clear.

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% with detailed parameter descriptions. The tool description does not add parameter-specific information beyond the schema, so baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a new task in an event-sourced task graph for multi-agent orchestration, with specific verb and resource. It distinguishes from sibling change_task_priority.

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

Usage Guidelines5/5

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

Explicit guidance: 'Use this to add work items before assigning them to agents' and 'For updating an existing task's priority, use change_task_priority instead'.

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/Mustafa-Ali-Ertugrul/allbrain-mcp'

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