Dandori

Lister les tâches

dandori_list_tasks

Read-onlyIdempotent

Lister les tâches ouvertes et celles terminées aujourd'hui, avec leurs sous-tâches. Filtres facultatifs, combinables

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

Input Schema

Name	Required	Description
`tag`	No	Filtrer par tag (nom)
`status`	No	Clé d'un statut : todo, in_progress, done ou un statut personnalisé
`date_to`	No	Date limite jusqu'à ce jour inclus (YYYY-MM-DD)
`goal_id`	No	Filtrer par objectif (tâches de l'objectif et de ses projets)
`priority`	No	Filtrer par priorité
`space_id`	No	Ne garder que cet espace (ID, champ spaces de dandori_daily_summary) ; par défaut tous
`date_from`	No	Date limite à partir de ce jour (YYYY-MM-DD)
`project_id`	No	Filtrer par projet

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The annotations already cover safety (readOnlyHint, idempotentHint, closed-world, non-destructive), so the bar is lower. The description still adds non-trivial behavior the annotations cannot: the default result set is open tasks plus today's completed tasks, and subtasks are returned nested. It omits ordering and any result-size limits.

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?

Two short clauses with no filler, and the default scope is front-loaded ahead of the filter note. The second clause is a fragment, but it earns its place by flagging filter combinability.

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 an 8-optional-parameter read tool with no output schema, the description covers what it returns at a high level. It leaves out sort order, any cap on the number of tasks returned, and how the date filters interact with the default 'open + done today' scope — gaps an agent would want before calling.

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 the schema already explains every filter, including enum values for priority and the date format. The description's contribution is only that filters may be combined, which is a small but real addition beyond the schema; baseline 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 names a specific verb and resource (lister les tâches) and scopes the result set precisely: open tasks plus those completed today, including subtasks. That scope separates it from the many dandori_list_* siblings even though no alternative is named 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?

It tells the agent that filters are optional and combinable, which is real usage guidance for an 8-parameter tool. It never says when to prefer this over sibling listers or when-not to use it, so the routing guidance is only implied.

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

All Dandori tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?