Skip to main content
Glama

doer_get_todo_list

Retrieve a todo list by ID to access its raw Markdown body, task checkboxes, pinned position, and optional rendered HTML preview.

Instructions

Get a todo list by ID, including its raw markdown body, task checkboxes, pinned position, and optional HTML preview

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": {
      "id": "<id>"
    },
    "name": "doer_get_todo_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the todo list
render_markdownNoWhether to include rendered GitHub Flavored HTML in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it partially meets it by enumerating the response payload (markdown body, checkboxes, pinned position, optional HTML preview). It says nothing about behavior on a missing/invalid ID, permissions, or whether the call has any side effects.

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 front-loaded sentence with the key action first and the return payload after it, with no filler. It is tight, though the trailing content list is dense enough that a little structure (e.g., separating scope from output) would aid scanning.

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?

For a two-parameter read tool with full schema coverage and no output schema, the description does the main extra work by telling the agent what comes back. Residual gaps are error behavior and permissions, which are secondary for a simple getter.

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 both parameters are already documented in the schema. The phrase "optional HTML preview" loosely echoes render_markdown but adds no syntax, format, or default detail beyond what the schema states.

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?

States a specific verb and resource ("Get a todo list by ID") plus the payload contents, which cleanly separates it from doer_list_todo_lists. It never explicitly names the sibling alternative, so sibling differentiation is implicit through "by ID" rather than stated.

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?

No when-to-use or when-not-to-use guidance appears anywhere in the sentence. An agent must infer from the tool name that this is the single-item fetch counterpart to the list tool; no prerequisites or alternatives are mentioned.

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