Skip to main content
Glama

Create a task from a TODO

taskhold_create_from_todo

Create a task from a TODO comment in code, keeping the file path and line number (label todo-from-code plus any labels you pass; priority as in taskhold_create; use taskhold_create for anything else). Returns the new task with its id and code location. Fails at the account's task ceiling or on an invalid project name.

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>",
      "file_path": "<file_path>",
      "line_number": "<line_number>"
    },
    "name": "taskhold_create_from_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTask title from the TODO
labelsNoMore labels besides todo-from-code, e.g. ["bug"]
projectNoProject name, e.g. the repo folder ("api-server"). Any case; created on first use. Easier than project_id.
priorityNoPriority (default medium; low unless it's a real bug)
file_pathYesPath of the file containing the TODO
descriptionNoExtra context from the code
line_numberYesLine number of the TODO

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, openWorld=false), and the description adds traits annotations cannot express: an implicit todo-from-code label is applied alongside supplied labels, the response includes the new task with id and code location, and failures occur at the account task ceiling or on invalid project names.

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?

A single dense paragraph with the core action front-loaded and the fallback routing parenthetically placed. Efficient, though the parenthetical stacks several distinct facts (labels, priority, alternative, return, failures) without visual separation.

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 no output schema, the description still states what is returned (the task with id and code location), names the two failure conditions, and explains label composition. For a 7-parameter creation tool with full schema coverage, nothing an agent needs to call it correctly 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 100%, so the baseline is 3. The description still adds meaning beyond the schema by explaining that labels are additive to the auto-applied todo-from-code label and by pointing at taskhold_create for priority conventions, though title/description/file_path are left to the schema.

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?

Specific verb and resource ("Create a task from a TODO comment in code") plus the scope distinction that it preserves file path and line number. That set of required fields (file_path, line_number) makes it unmistakably different from taskhold_create.

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?

Explicitly routes: use this for TODOs found in code, "use taskhold_create for anything else," and references taskhold_create for priority semantics. Both the use case and the catch-all alternative are stated, so an agent has no inference left to do.

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