Skip to main content
Glama
dantalan

baatjie-mcp-server

by dantalan

List Todos With Sequencing

baatjie_list_todos
Read-onlyIdempotent

List todos with wave, track, effort, and blocker counts for a complete board overview. Filter by status, priority, or workstream to focus on specific tasks.

Instructions

List todos with their wave, track, effort, blocker count and unblock count.

Use this for a full picture of the board. For "what do I do next", baatjie_next_actions is the better tool because it filters to what is actually actionable.

Args:

  • status ('open' | 'in_progress' | 'done' | 'blocked', optional): Filter by status. Omit to return everything except done.

  • track ('A' | 'B' | 'SPINE' | 'TODAY', optional): Filter by workstream

  • wave (number, optional): Filter by wave (0=today, 1=roots, 2..4=later)

  • priority ('critical' | 'high' | 'medium' | 'low', optional): Filter by priority

  • limit (number): Max items (default: 25)

  • offset (number): Pagination offset (default: 0)

  • response_format ('markdown' | 'json'): Output format

Returns: { "total","count","offset","items":[...],"has_more","next_offset"? } where each item carries id, title, priority, status, wave, track, effort, open_blockers, startable and unblocks.

Examples:

  • "Show the critical list" -> priority='critical'

  • "What's in wave 1?" -> wave=1

  • "Everything on the housing rail" -> track='B'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waveNo
limitNoMaximum rows to return (1-200, default 25)
trackNo
offsetNoRows to skip, for pagination
statusNoFilter by status; omit for all non-done
priorityNo
response_formatNoOutput format: 'markdown' for human-readable, 'json' for machine-readablemarkdown
Behavior4/5

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

Although the annotations already declare the tool read-only and idempotent, the description adds behavioral detail by stating the default status filter ('Omit to return everything except done'), pagination semantics, and the shape of the response. It doesn't contradict annotations and provides useful context beyond the structured metadata.

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 well-structured into a summary, usage context, Args list, Returns shape, and Examples. Every section carries informative content without fluff. The formatting makes it easy to scan, and the examples are concise yet illustrative.

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?

Despite lacking an output schema, the description fully specifies the return structure ('total', 'count', 'offset', 'items', 'has_more', 'next_offset') and item fields. It also covers defaults, pagination, and response formats, making the tool usable without needing to probe the schema or guess behavior.

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?

The description's Args block goes beyond the schema's raw enums by explaining wave meaning ('0=today, 1=roots, 2..4=later'), the default behavior of omitting status, and practical examples mapping natural language to parameter values (e.g., "Show the critical list" -> priority='critical'). With 57% schema coverage, this compensation is necessary and successful.

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?

The description starts with a specific verb and resource: 'List todos with their wave, track, effort, blocker count and unblock count.' It clearly differentiates from the sibling tools like baatjie_next_actions by explaining what this tool covers (full board picture) versus the alternative. The examples further cement its purpose.

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?

The description explicitly states when to use this tool: 'Use this for a full picture of the board.' It also calls out a better alternative for a specific need: 'For "what do I do next", baatjie_next_actions is the better tool because it filters to what is actually actionable.' This is a clear, actionable usage guideline.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dantalan/baatjie-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server