Skip to main content
Glama

Trier un élément de capture

dandori_inbox_convert

Transformer un élément de Capture en tâche, note ou envie ; l'élément quitte Capture

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": {
      "id": "<id>",
      "target_type": "<target_type>"
    },
    "name": "dandori_inbox_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID de l'élément de capture
doneNoTâche : true si c'est déjà fait (la tâche naît terminée)
contentNoNote : contenu (le texte capturé devient le titre)
goal_idNoTâche : ID de l'objectif
categoryNoEnvie : catégorie (défaut autre)
deadlineNoTâche : échéance (YYYY-MM-DD)
project_idNoTâche : ID du projet
target_typeYesCe qu'il devient : task, note ou wish (envie, plan Plus requis)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare the generic mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds the substantive behavioral fact that the source item leaves Capture, i.e. this is a move-and-transform rather than a copy — exactly the kind of context annotations do not carry. It does not say whether the removed capture item is recoverable or what the call returns.

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 the transformation outcome placed first and the side effect after the semicolon; nothing is redundant. It is tightly written, though the terseness leaves the guidance gaps noted above.

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-parameter mutation with no output schema, the description covers the core transformation and the source-item removal but omits what comes back (presumably the new task/note/wish and its ID) and any error behavior for invalid targets. Combined with the 100% schema coverage and existing annotations, it is adequate but not complete.

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 every one of the 8 parameters (id, target_type, done, content, goal_id, category, deadline, project_id) is already documented, including the per-target-type applicability and the Plus-plan requirement for wish. The description only restates the task/note/wish target mapping and adds no new syntax or constraint beyond the schema, so 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 (Transformer/convert), the source resource (un élément de Capture), the three possible targets (tâche, note ou envie) and the resulting state change ('l'élément quitte Capture'). That is enough to distinguish it from generic creators like dandori_create_task or dandori_create_note, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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?

Usage is only implied: an agent can infer it is for triaging items that already sit in Capture, as opposed to creating something from scratch. There is no explicit when-to-use/when-not statement, no mention of prerequisites such as which capture states are convertible, and no pointer to a sibling for the alternative path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources