Skip to main content
Glama

create_task

Create a task with title (required), optional labels, due date, priority, project, description, and evidence policy.

Instructions

Create a new task in Delega

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelsNoLabels to apply
contentYesTask title / content
due_dateNoDue date in YYYY-MM-DD format
priorityNoPriority: 1=normal, 2=medium, 3=high, 4=urgent
project_idNoProject ID to assign to
descriptionNoDetailed description
evidence_policyNoSet 'required' to force structured completion evidence (commit/PR/CI/etc.) before this task can be completed
Behavior2/5

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

No annotations exist, and the description only states the action without disclosing effects (e.g., return value, permissions, side effects). Minimal transparency for a mutation tool.

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?

Single sentence, no wasted words, front-loaded with key information. Highly concise.

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 7 parameters (1 required), no output schema, and many sibling tools, the description is too terse. Lacks details on return values, error handling, or how parameters affect behavior.

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 has 100% description coverage for all 7 parameters. The tool description adds no extra meaning, so baseline score 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?

Description uses a specific verb 'Create' and specific resource 'a new task in Delega'. It clearly distinguishes from sibling tools like 'update_task', 'delete_task', and 'get_task'.

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 on when to use this tool versus alternatives (e.g., update_task, assign_task). Does not specify prerequisites or exclusions.

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/delega-dev/delega-mcp'

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