huly-mcp-selfhost

list_todos

Read-only

Retrieve your planner to-dos in planner order, open items by default, and filter by status or due date to see what needs attention.

Instructions

List your own planner to-dos: open by default, in planner order; filter by status or due date

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	Default
`limit`	No
`status`	No		open
`dueBefore`	No	ISO date
`workspace`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.1Nov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful behavior beyond that: results are limited to the caller's own to-dos and returned in planner order. It says nothing about pagination limits or what the workspace scoping does, so disclosure is partial.

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 no wasted framing; scope, default, ordering and filters all appear immediately. Minor redundancy with the schema's status default of 'open', and the semicolon packing makes it slightly dense.

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?

For a four-parameter list tool with no output schema and low schema coverage, the description covers defaults, ordering, and two filters but omits the meaning of 'workspace' and 'limit'. An agent could call it, but not with full confidence about scoping or result volume.

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 coverage is only 25%, so the description must carry meaning, and it does explain the status and due-date filters along with the open-by-default behavior. However, the 'workspace' and 'limit' parameters are left unexplained in both schema and description, so it only partially compensates.

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 names a specific verb and resource ('List your own planner to-dos') and scopes it to the caller's own items, which separates it from the many list_* siblings covering other resources. It stops short of explicitly routing to an alternative tool, but the resource is unambiguous.

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?

It implies default behavior ('open by default') and mentions filtering by status or due date, giving a hint of when to pass filters. There is no explicit when-not guidance, no note about the 'all' status value, and no comparison to any sibling tool.

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

Deploy Server