Skip to main content
Glama

doer_create_todo_list

Create a markdown todo list or checklist in Doer and attach it to a project or keep it standalone.

Instructions

Create a new markdown todo list or checklist in Doer (assigned to a project or kept standalone)

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": "doer_create_todo_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoRaw markdown content of the todo list (checklists with - [ ] items)
titleYesTitle of the todo list
pinnedNoWhether the todo list should be pinned to the Doer sidebar
project_idNoAssociated project ID, or null for a standalone scratchpad todo list
pinned_positionNoSequential ordering position among pinned lists

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose permissions, side effects, validation behavior, whether creation is reversible, or what the tool returns after creating the list.

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?

The description is a single front-loaded sentence with no wasted wording. It states the action, resource, format, and scope efficiently.

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?

The schema fully describes the parameters, and the description covers the core create action plus project/standalone scope. However, with no annotations and no output schema, it leaves behavioral details such as return value and side effects unaddressed.

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%, so the schema already documents all five parameters. The description adds only a small amount of meaning by noting that the list can be assigned to a project or kept standalone, which maps to the project_id null case.

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 new markdown todo list or checklist in Doer. It also clarifies the project-vs-standalone scope, though it does not explicitly distinguish itself from siblings like append or update.

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?

It implies use for new lists by saying 'Create a new,' but gives no explicit when-to-use guidance versus alternatives such as doer_append_to_todo_list or doer_update_todo_list. The project/standalone note is contextual, not comparative.

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