gryzzly-mcp

create_task

Create a task in a project to enable time logging; check existing tasks first to avoid duplicates.

Instructions

Create a task in a project, both named or identified. Tasks are what time is declared against, so a project needs at least one before log_time works. A task with is_container true only holds other tasks and takes no time; a subtask names its parent. planned_duration and estimated_duration accept human durations (40h, 90m). Check list_tasks first, since a second call creates a duplicate.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	The task's name.
`tags`	No	Tag names to attach.
`end_at`	No	When the task is supposed to end.
`groups`	No	Group identifiers to assign.
`parent`	No	The parent task, by name or id, when this is a subtask.
`project`	Yes	The project it belongs to, by name, code or id.
`start_at`	No	When the task starts. Required by Gryzzly. Defaults to today.
`budget_type`	No	How the budget is expressed.
`hourly_rate`	No	The hourly rate, when the type calls for one.
`is_container`	No	Whether this task only holds other tasks. A container takes no time.
`budget_amount`	No	The budget amount, when the type calls for one.
`hourly_rate_mode`	No	Where the hourly rate comes from.
`planned_duration`	No	Planned time, as a duration (`40h`, `3600s`, `90m`).
`estimated_duration`	No	Estimated time, as a duration.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The task's identifier.
`name`	No	The task's name.
`tags`	No	The tags attached to the task.
`end_at`	No	When the task is supposed to end.
`groups`	No	The groups assigned to the task.
`start_at`	No	When the task starts.
`parent_id`	No	The parent task, when this task is a subtask.
`created_at`	No	When the task was created.
`project_id`	No	The project the task belongs to.
`updated_at`	No	When the task was last updated.
`budget_type`	No	One of `none`, `detailed`, `global`, `time`.
`hourly_rate`	No	The task's hourly rate.
`completed_at`	No	When the task was completed.
`is_container`	No	Whether the task only holds other tasks.
`budget_amount`	No	The task's budget.
`hourly_rate_mode`	No	One of `task`, `group`, `contributor`.
`planned_duration`	No	Planned duration, in seconds.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare non-readOnly, non-destructive, non-idempotent, open-world behavior; the description reinforces non-idempotency by warning that repeat calls duplicate. It also adds semantics the annotations cannot carry: container tasks take no time, subtasks name a parent, and tasks are the unit that log_time declares against.

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?

Four sentences, front-loaded with the core purpose and then the operational caveats. Dense but each sentence carries a distinct fact (dependency, container semantics, duration format, duplicate risk); no filler.

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?

With an output schema present, return values need no explanation, and the annotations cover the safety profile. The description fills the remaining gaps an agent needs: required context (project, optional parent), the log_time dependency, duration syntax, and the duplicate hazard.

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% across 14 parameters, so the schema already documents each field, including the duration format examples. The description restates is_container/subtask behavior and the 40h/90m duration format that the schema's own descriptions already provide, adding little beyond the 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?

States a specific verb+resource (create a task) plus the scoping detail that it lives in a project identified by name or id. An agent can separate this from create_project, update_task, or delete_task from the description alone.

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

Usage Guidelines4/5

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

Explicitly routes the agent to list_tasks first and explains why (a second create call produces a duplicate), which is real when-to-use guidance. It also discloses the cross-tool dependency that log_time requires at least one task, though it never states an outright 'do not use when' condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.