Skip to main content
Glama

create_task

Create a new task with title, description, status, priority, dates, assignees, tags, and task relationships like subtasks, blockers, and related tasks.

Instructions

Create a new task with title, description, status, priority, size, dates, dartboard, assignees, tags, and task relationships (subtasks, blockers, related tasks)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTask title (max 500 chars)
descriptionNoTask description (markdown supported)
dartboardYesDartboard dart_id (use get_config to find)
statusNoStatus name or dart_id
priorityNoPriority 1-5 (1=lowest, 5=highest)
sizeNoSize estimate 1-5
assigneesNoArray of assignee dart_ids
tagsNoArray of tag dart_ids
due_atNoDue date (ISO8601)
start_atNoStart date (ISO8601)
parent_taskNoParent task dart_id for subtasks
subtask_idsNoIDs of tasks that are subtasks (children) of this task. Each ID must be a valid dart_id format.
blocker_idsNoIDs of tasks that block this task from being started or completed. Each ID must be a valid dart_id format.
blocking_idsNoIDs of tasks that this task is blocking. Each ID must be a valid dart_id format.
duplicate_idsNoIDs of tasks that are duplicates of this task. Each ID must be a valid dart_id format.
related_idsNoIDs of tasks that are related to this task (loosely connected). Each ID must be a valid dart_id format.
commentNoOptional comment to add after creating the task (non-blocking)
Behavior3/5

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

No annotations provided; description carries full burden. It notes the optional comment is non-blocking, which is helpful, but omits side effects like validation, permission requirements, or behavior on failed relationships. Adequate but not comprehensive.

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?

Single sentence efficiently lists all capabilities without verbosity. Front-loaded with action and key parameters. Slightly long but each part is necessary, so no waste.

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?

Description covers all parameter categories but lacks return value information (no output schema). For a creation tool with 17 parameters, it is complete in scope but could benefit from stating what is returned (e.g., task ID). Adequate but not thorough.

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 coverage is 100%, so baseline is 3. Description groups parameters (e.g., 'dates') but adds minimal new meaning beyond the schema's individual descriptions. It doesn't explain parameters not in schema (none), so score remains baseline.

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?

Description clearly states 'Create a new task' with a comprehensive list of attributes, making the purpose explicit and specific to task creation. It distinguishes from sibling tools like update_task or add_task_comment by focusing on creation with all supported fields.

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?

No explicit guidance on when to use this tool versus alternatives. For a creation tool, context is implied but not stated. Siblings like batch_create are absent, so missing guidance on when to prefer single vs batch creation.

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/standardbeagle/dart-query'

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