Skip to main content
Glama

create_task

Create a task for the planner to schedule. Estimate a realistic duration if the user gave none and say so in your answer. Don't set block limits if not specifically asked.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "durationMinutes": "<durationMinutes>"
    },
    "name": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
titleYes
deadlineNoDue by; a bare date means end of day
priorityNo1 = niedrig, 2 = normal, 3 = hoch, 4 = kritisch
hoursTypeNoWhere the planner puts it: "work" (default) inside working hours, "personal" for private things planned outside working hours, in the user's personal time (evenings, weekends)
autoScheduleNoWhether the planner puts the task in the calendar. Tasks imported from Jira or GitHub start with false until the user picks them; set true to plan one, false to keep it on the list without planning it
earliestStartNoNot before
durationMinutesYesTotal time the task needs
maxBlockMinutesNoThis task's own cap on one block. Don't set block limits if not specifically asked. Without it the task follows the user's setting (no cap unless they set one); null removes the task's own cap
minBlockMinutesNoShortest block worth planning. Don't set block limits if not specifically asked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint false, destructiveHint false), the description adds that the task is for the planner to schedule and imposes two behavioral rules: estimate duration if absent and avoid block limits unless requested. It does not describe return behavior, validation failures, or scheduling side effects, but the annotation baseline is covered.

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 short sentences, front-loaded with purpose and followed by the two most important behavioral rules. No unnecessary wording or repetition.

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

Completeness4/5

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

With 10 parameters but rich schema descriptions and no output schema, the description supplies the key missing behavioral guidance: duration estimation and block-limit avoidance. It does not address how scheduling interacts with autoSchedule, hoursType, or priority, but the schema carries those details adequately.

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?

Schema coverage is high at 80% and already documents most parameters well. The description adds meaning for the required durationMinutes by instructing the agent to estimate when the user gives none, and reinforces the maxBlockMinutes/minBlockMinutes constraint, though the block-limit guidance is largely duplicated from the schema.

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

Purpose4/5

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

The description states a specific verb and resource: create a task for the planner to schedule. This distinguishes it from generic task creation and hints at calendar planning, though it does not explicitly differentiate from update_task or create_habit.

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?

It gives clear invocation guidance: estimate duration when the user provides none and disclose that in the answer, and avoid block limits unless specifically asked. It lacks explicit when-to-use guidance versus alternatives like update_task, but the conditions it does provide are actionable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources