Skip to main content
Glama

obsidian_append_journal

Adds a structured daily journal entry to the top of an Obsidian balance journal, capturing successes, tomorrow's priorities, and improvement notes.

Instructions

Insère une entrée quotidienne structurée dans 03 - Vie Perso/Journal de Bilan.md en tête de l'historique

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": {
      "date": "<date>",
      "subtitle": "<subtitle>",
      "success_bullets": "<success_bullets>"
    },
    "name": "obsidian_append_journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate au format YYYY-MM-DD
subtitleYesSous-titre (ex: 'Bilan Quotidien', 'Session Code & Musculation')
success_bulletsYesListe des points 'Ce qui a marché'
priorities_bulletsNoListe des points 'Priorités fixées pour demain'
improvements_bulletsNoListe des points 'Ce qui n'a pas marché & Pourquoi'

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?

With no annotations, the description carries the full disclosure burden, and it does add one genuinely behavioral fact: the entry is prepended at the top of the history rather than appended to the end. It is silent on key mutation behavior for a hard-coded write target — whether an existing entry for the same date is overwritten or duplicated, whether the file is created if absent, and what confirmation is returned.

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 zero filler; the verb, target file, and insertion position come in one pass. It is efficient, though the extreme terseness leaves it doing only the bare minimum framing for a five-parameter write operation.

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?

This is a mutation against a fixed vault file with no annotations and no output schema, yet the description does not say how duplicates for the same date are handled, whether the target file must already exist, or what the caller gets back. For a tool that silently writes into a user's journal, those omissions are material.

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 parameter including date format, subtitle examples, and the three bullet lists is already documented in the schema. The description only gestures at 'entrée structurée', adding no field-level meaning beyond what is structured, which is the expected baseline here.

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

Purpose5/5

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

States a specific verb ('Insère'), a specific resource ('une entrée quotidienne structurée'), the exact target file ('03 - Vie Perso/Journal de Bilan.md') and the insertion point ('en tête de l'historique'). No sibling in the list appends journal entries, and the file path alone makes the tool unmistakable.

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?

The daily-journal framing implies when the tool is appropriate, and the fixed file path reinforces that it is for personal daily bilan entries rather than general note writing. However, there is no explicit statement of when to prefer this over obsidian_read_note or the backlog tools, and no exclusions or preconditions are given.

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