Skip to main content
Glama

obsidian_add_backlog_task

Add a checkbox task to Obsidian's Backlog.md under a selected priority and life domain, organizing personal tasks by urgency and category.

Instructions

Ajoute une action à cocher dans 03 - Vie Perso/Backlog.md sous le niveau de priorité et le domaine choisis

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": {
      "priority": "<priority>",
      "domain": "<domain>",
      "task": "<task>"
    },
    "name": "obsidian_add_backlog_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesDescription de la tâche concrète à accomplir
domainYesCompartiment de vie cible
priorityYesNiveau de priorité (P1: Immédiat, P2: Important, P3: Fond)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the entry is inserted as a checkbox under a priority-level and domain heading in a specific file, but it says nothing about permissions, whether the file is created if missing, append-only vs. overwrite behavior, or what happens with duplicate tasks.

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 that names the action, the target file and the ordering keys with no filler. It is arguably too terse rather than too long, but nothing is wasted.

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

Completeness4/5

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

For a 3-parameter write tool with a fully documented schema, no output schema, and all required fields covered, the description provides enough to call it correctly. Remaining gaps (file-existence behavior, failure modes) are moderate rather than blocking.

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% and both enums are self-documenting, so the schema already does the heavy lifting. The description adds partial value by indicating that 'priority' and 'domain' select the section under which the task is filed, but it does not clarify the free-text task format or any length/format constraints.

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 pairs the verb 'Ajoute' with a concrete resource ('une action à cocher') and even names the target file (03 - Vie Perso/Backlog.md), so the agent knows exactly what is created and where. It does not distinguish itself from siblings such as obsidian_append_journal, so it stops short of a 5.

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: the phrasing suggests capturing a personal todo into a backlog under a priority/domain section. There is no explicit when-to-use statement, no mention of when to prefer obsidian_append_journal or another note-writing sibling, and no prerequisites such as the file needing to exist.

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