Skip to main content
Glama

doer_list_todo_lists

Search and list Markdown todo lists by project, standalone or pinned status, and keyword, with pagination controls to locate and review tasks.

Instructions

Search and list todo lists with filtering by project, standalone status, pinned status, or keyword

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "doer_list_todo_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFull-text search query across todo list title and markdown body
limitNoNumber of todo lists to return (default 50, max 100)
scopeNoScope filter: 'standalone' (unassigned scratchpad lists) or 'all'
offsetNoPagination offset (default 0)
pinnedNoFilter by pinned status (true = only pinned, false = only unpinned)
project_idNoFilter todo lists belonging to a specific project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden; 'Search and list' does make clear this is a non-mutating read, which is the key behavioral signal. It says nothing about result ordering, whether an empty match returns an empty array or an error, or how pagination interacts with a total count, all of which an agent would benefit from knowing.

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?

A single sentence that front-loads the action and then the filter dimensions, with no filler or redundancy. Every clause maps to a real capability of the tool.

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 simple filtered-list tool with all six parameters fully described in the schema and no output schema to explain, the description covers what is needed to select and call it. The only shortfall is the absence of any tie-breaker against the single-list and project-listing siblings.

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 every parameter (q, limit, scope, pinned, offset, project_id) already carries its own documentation including defaults and bounds. The description restates the filter set without adding meaning beyond the schema, so the baseline of 3 applies.

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 gives a specific verb pair ('Search and list') plus the resource ('todo lists') and enumerates the available filter dimensions, so an agent immediately knows this is the read path for todo lists. It stops short of naming siblings such as doer_get_todo_list to draw the boundary explicitly.

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

Usage Guidelines3/5

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

Use is implied by the enumeration of filters — an agent can infer this is the tool for browsing/finding lists rather than fetching a single known list. There is no explicit when-to-use or when-not-to-use statement, and the single-list sibling is never named as the alternative.

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