Skip to main content
Glama

Create a task

taskhold_create

File work for later (a bug, a follow-up, a chore); it lands in To Do. To file and start at once: taskhold_begin. parent_task_id adds one step to a task (taskhold_plan for several). Returns id, status and priority. Fails on an unknown parent_task_id or a step as parent, an unknown project_id (pass project by name) or at the task ceiling.

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>"
    },
    "name": "taskhold_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTask title
labelsNoLabels, e.g. ["bug", "refactor"]
repeatNoRepeat it: "every monday at 9am", "weekdays 8:30", "monthly on the 1st", "every 3 days". Adds a To Do copy unless the last is open.
projectNoProject name, e.g. the repo folder ("api-server"). Any case; created on first use. Easier than project_id.
priorityNoPriority (default medium)
project_idNoProject id (project, a name, is easier)
descriptionNoDetails (markdown)
parent_task_idNoMake it a step (subtask) of this top-level task

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / project / description
      Previous value: -"Project name, e.g. the repo folder (\"api-server\"). Matched case-insensitively; created on first use. Use this instead of project_id."New value: +"Project name, e.g. the repo folder (\"api-server\"). Any case; created on first use. Easier than project_id."
    • addedInput schema / properties / repeat
      Added value: +{
      +  "description": "Repeat it: \"every monday at 9am\", \"weekdays 8:30\", \"monthly on the 1st\", \"every 3 days\". Adds a To Do copy unless the last is open.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / parent_task_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive write, so the description carries real weight and does: it names the resulting state (To Do), the returned fields (id, status, priority), and four concrete failure conditions including the task ceiling and passing a step as parent. It stops short of describing cascading effects or what happens to repeat-generated copies beyond what the schema states.

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?

Front-loaded with the purpose, then alternatives, then return value, then failure modes — a sensible order with no filler sentences. The compression is heavy in places ('pass project by name', the run-on failure list), which costs a little readability but not accuracy.

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?

For an eight-parameter creation tool with no output schema, the description covers default state, return fields, the sibling to use for immediate work, subtask semantics, and the failure surface. Nothing an agent needs before calling it is missing.

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 already 100%, so the baseline is 3, but the description adds genuine semantics: parent_task_id turns the new task into a single step (with taskhold_plan for multiple), and it reinforces preferring project name over project_id. These are relationships the schema fields do not express on their own.

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 and resource ('File work for later ... it lands in To Do') with concrete examples of what counts (bug, follow-up, chore), and explicitly distinguishes itself from taskhold_begin. An agent can distinguish it from siblings without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: use this to file for later, use taskhold_begin to file and start immediately, and use taskhold_plan when adding several steps instead of one. Names both alternatives and the condition that selects each.

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