Dandori

Créer une tâche

dandori_create_task

Créer une nouvelle tâche

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "dandori_create_task"
  }
}

Input Schema

Name	Required	Description
`tags`	No	Noms des tags à associer (créés automatiquement s'ils n'existent pas)
`notes`	No	Notes complémentaires
`title`	Yes	Titre de la tâche
`status`	No	Clé du statut : todo, in_progress, done, archived ou un statut personnalisé (voir dandori_list_task_statuses)
`goal_id`	No	ID de l'objectif
`deadline`	No	Date limite (YYYY-MM-DD)
`due_time`	No	Heure de la tâche (HH:MM), seulement avec une date limite
`priority`	No
`space_id`	No	ID de l'espace (champ spaces de dandori_daily_summary) ; une tâche d'un projet prend toujours l'espace du projet
`project_id`	No	ID du projet
`description`	No	Description
`energy_level`	No	Niveau d'énergie requis
`recurrence_type`	No	Récurrence
`estimated_duration`	No	Durée estimée en minutes
`recurrence_interval`	No	Intervalle de récurrence (ex. 2 = toutes les 2 semaines)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

C2.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation/safety profile is covered. The description adds nothing on top: no mention that tags are auto-created, that a task inherits its project's space, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the brevity is under-specification rather than efficiency: the single phrase conveys no information beyond the tool's own name and could be deleted without any loss.

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?

For a 15-parameter creation tool with no output schema, the description should at least note required fields, tag auto-creation, or the space/project constraint. Instead it is a bare phrase, leaving the schema to carry nearly the entire burden of correct invocation.

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 93% across 15 parameters, so the schema already explains title, status keys, deadline format, recurrence, and the project/space relationship. The description adds no additional meaning, which is the baseline-3 case when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Créer une nouvelle tâche" only restates the tool name and title (dandori_create_task / "Créer une tâche"). It does not say what distinguishes this from dandori_apply_task_template, dandori_create_goal or dandori_update_task, nor what a created task contains.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives such as applying a template or updating an existing task. The agent must infer from the name alone that this is the entry point for task creation.

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?