nudge

list_todos

Retrieve your tasks with optional filters for status, due date, and priority. Quickly see what's pending, overdue, or completed.

Instructions

List the user's tasks with optional filters. Use this when asked directly, or when you need context to give a useful, honest answer about where things stand.

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

Input Schema

Name	Required	Description
`tag`	No	Filter by a specific tag or label.
`done`	No	true = completed only, false = pending only. Omit for all.
`overdue`	No	Only tasks past their due date and still open.
`priority`	No
`due_today`	No	Only tasks due today.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jul 12, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. Only states it lists with filters, with no disclosure of read-only nature, return format, or side effects. Agents lack important behavioral context.

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?

Two sentences, directly front-loaded with action and filters. No wasted words; every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 optional parameters, no output schema, and no annotations, the description is too sparse. It omits details on default behavior (e.g., returns all tasks if no filters), ordering, or pagination, leaving agents underinformed.

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 80%, so description does not need to add much. The description merely says 'optional filters', adding no extra meaning beyond what the schema already provides for parameters.

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?

Clearly states 'List the user's tasks with optional filters', which specifies the verb and resource. Does not explicitly differentiate from siblings like search_todos or get_pending_today, but the primary purpose is clear.

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?

Says 'Use this when asked directly, or when you need context to give a useful, honest answer about where things stand', which provides some usage context but no exclusions or comparisons with alternatives.

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

Deploy Server