Skip to main content
Glama

create_task

Create a task with title, project, owner, notes, due date, and optional recurrence that auto-generates next occurrence upon completion. Supports subtasks.

Instructions

Create a new task in the SQLite database.

Args:
    title: Short task description.
    project_id: Which project this task belongs to.
    owner: Who is responsible (default "Metis").
    notes: Additional details or context.
    due_date: Optional due date in YYYY-MM-DD format.
    recurrence: Optional repeat — "daily", "weekly", "monthly", or "yearly".
                When a recurring task is completed, the next occurrence is created automatically.
    parent_task_id: Optional parent task — set this to make this a subtask.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
project_idYes
ownerNoMetis
notesNo
due_dateNo
recurrenceNo
parent_task_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations exist, so the description carries full burden. It only reveals that recurring tasks auto-create next occurrences, but omits other behavioral traits like side effects, authentication requirements, or what happens on validation failure.

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 uses a clear Args structure but is somewhat verbose. The main purpose is not front-loaded; it starts directly with parameter descriptions. Every line adds value, but conciseness could be improved.

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 7 parameters (2 required) and no annotations, the description covers parameter meanings and recurrence behavior but does not mention output schema or return format. It is adequate but not fully complete.

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 compensates by explaining each parameter's role (e.g., 'owner: Who is responsible (default "Metis")', 'recurrence: Optional repeat...'). It adds meaning beyond parameter names and types.

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 explicitly states 'Create a new task in the SQLite database', with a specific verb and resource. It clearly differentiates from sibling tools like add_glossary_term or update_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 is provided on when to use this tool versus alternatives like update_task or add_journal_entry. The description lacks context about prerequisites, when creation is appropriate, or when other tools should be preferred.

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/SVerITG/Metis_PH'

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