kObsidian MCP

Append Wiki Log Entry

wiki.logAppend

Append a dated wiki log entry with operation kind, title, optional body, and refs. Use to record decisions or notes in a grep-friendly format.

Instructions

Append one typed entry to wiki/log.md in the canonical format ## [YYYY-MM-DD] <op> | <title>, optionally followed by a body and a Refs: list. The format is chosen so grep '^## \[' log.md | tail -20 is a valid 'recent activity' query. Use this when the agent makes a wiki-meaningful action that no other wiki.* tool already logs (e.g. a decision or note); ingest and merge log themselves. Auto-runs wiki.init if the wiki has not been scaffolded yet. Idempotent only in the trivial sense — every call appends a new entry.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Examples:

Example 1 — Log an architectural decision with two refs.:

{
  "op": "decision",
  "title": "Adopt gRPC for internal RPC",
  "body": "Streaming + typed schemas outweigh the browser-edge tax.",
  "refs": [
    "wiki/Sources/adr-004.md",
    "wiki/Concepts/grpc.md"
  ]
}

Example 2 — Quick freeform note dated today.:

{
  "op": "note",
  "title": "Reviewed orphan pages from last sprint"
}

Input Schema

TableJSON Schema

Name	Required	Description
`op`	Yes	Log entry kind: ingest \| query \| lint \| note \| decision \| merge. Becomes the `<op>` token in `## [YYYY-MM-DD] <op> \| <title>`.
`body`	No	Optional markdown body written under the heading. Omit for a heading-only entry.
`date`	No	YYYY-MM-DD override for the entry date. Defaults to today.
`refs`	No	Optional list of vault-relative paths or wiki-link targets rendered as a `Refs:` list under the entry.
`title`	Yes	One-line title for the entry. Becomes the `<title>` token in the heading.
`wikiRoot`	No	Per-call wiki directory override.
`vaultPath`	No	Per-call vault override.

Output Schema

TableJSON Schema

Name	Required	Description
`target`	Yes	The path or identifier the tool acted on.
`changed`	Yes	True if the tool altered vault state on this call; false if it was a no-op.
`summary`	Yes	Short human-readable summary of what happened.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.5Aug 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed7 schema fields changedv0.3.2May 9, 2026

addedInput schema / properties / body / description

Added value: +"Optional markdown body written under the heading. Omit for a heading-only entry."

addedInput schema / properties / date / description

Added value: +"YYYY-MM-DD override for the entry date. Defaults to today."

addedInput schema / properties / op / description

Added value: +"Log entry kind: ingest | query | lint | note | decision | merge. Becomes the `<op>` token in `## [YYYY-MM-DD] <op> | <title>`."

addedInput schema / properties / refs / description

Added value: +"Optional list of vault-relative paths or wiki-link targets rendered as a `Refs:` list under the entry."

addedInput schema / properties / title / description

Added value: +"One-line title for the entry. Becomes the `<title>` token in the heading."

addedInput schema / properties / vaultPath / description
```
Added value: +"Per-call vault override."
```
addedInput schema / properties / wikiRoot / description
```
Added value: +"Per-call wiki directory override."
```

Changed4 schema fields changedv0.1.2Apr 25, 2026

addedOutput schema / description

Added value: +"Standard mutation envelope. Individual tools may attach additional fields (e.g. `created`, `appended`, `before`/`after` counts) — those are documented in the tool description."

addedOutput schema / properties / changed / description

Added value: +"True if the tool altered vault state on this call; false if it was a no-op."

addedOutput schema / properties / summary / description

Added value: +"Short human-readable summary of what happened."

addedOutput schema / properties / target / description

Added value: +"The path or identifier the tool acted on."

First observedv0.1.0Apr 24, 2026

TDQS

A5/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It explicitly states that every call appends a new entry, that the tool may auto-run `wiki.init` if the wiki is not scaffolded, and how the active vault is resolved. These are meaningful side effects an agent needs to know before invoking.

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

Conciseness5/5

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

The description is front-loaded with the core action and format, followed by usage guidance, side effects, and examples. Every sentence earns its place, and the examples are placed at the end where they complement rather than obscure the operational guidance.

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

Completeness5/5

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

Given 7 parameters, sibling logging tools, and no annotations, the description covers the critical context: purpose, exact file format, when to use it, side effects, vault resolution, and concrete examples. The presence of an output schema means the response shape does not need to be spelled out in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds real value beyond the schema: it explains how `op` and `title` map into the heading, how `refs` render, that `date` defaults to today, and that `vaultPath` overrides the session-active vault. The two JSON examples clarify realistic usage for multiple parameters at once.

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?

The description names the exact resource (`wiki/log.md`), the verb (`Append`), and the canonical heading format, making the tool's function immediately clear. It also differentiates itself from sibling tools by noting that `ingest` and `merge` log themselves, so an agent can tell which actions belong here.

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

Usage Guidelines5/5

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

The description gives an explicit trigger: 'Use this when the agent makes a wiki-meaningful action that no other `wiki.*` tool already logs', with concrete examples like `decision` and `note`. It also names exclusions (`ingest` and `merge` log themselves) and explains the vault-selection precedence with `vaultPath`.

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

Deploy Server