Skip to main content
Glama
bezata

kObsidian MCP

by bezata

Merge Summary Into Concept Or Entity Page

wiki.summaryMerge

Adds a cited section to an existing concept or entity page, creating the page with canonical frontmatter if missing. Includes citation source, quote, and updates frontmatter.

Instructions

Add a cited section to an EXISTING Concepts/ or Entities/ page, or create the page with canonical frontmatter if targetPath does not exist. The new section is rendered under heading (default: Update YYYY-MM-DD); citationSource adds a [[wiki-link]] to the source and pushes it onto the page's sources: frontmatter list, and citationQuote renders as a blockquote under the citation. On existing pages, updated: frontmatter is bumped to today. Use this when filing a follow-up onto a known page; use wiki.ingest instead when bringing in a NEW source (which auto-creates Sources/<slug>.md). When creating a new entity page, entityKind is required.

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 — Append a 'Notable Facts' section to an existing concept page, citing one source with a quote.:

{
  "targetPath": "wiki/Concepts/circuit-breaker.md",
  "heading": "Notable Facts",
  "newSection": "Adopted by payment-service after the 2026-04-10 cascade incident.",
  "citationSource": "wiki/Sources/postmortem-2026-04-10-payment-timeouts-cascade.md",
  "citationQuote": "Timeouts in payment-service propagated to order-service within 14s."
}

Example 2 — Create a new entity page for an organization on first reference.:

{
  "targetPath": "wiki/Entities/anthropic.md",
  "pageType": "entity",
  "entityKind": "org",
  "newSection": "AI safety lab; publisher of the Model Context Protocol.",
  "summary": "AI safety company behind Claude and MCP."
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aliasesNoSet or replace the page's frontmatter `aliases` list.
headingNoH2 heading text for the new section (e.g. 'Notable Facts'). Defaults to a timestamped 'Update YYYY-MM-DD' heading.
summaryNoSet or replace the page's frontmatter `summary` field.
pageTypeNoPage type used when creating a missing target page. Picks the matching frontmatter schema.concept
wikiRootNoPer-call wiki directory override.
vaultPathNoPer-call vault override.
entityKindNoRequired only when creating a missing entity page. One of person | place | org | work | other.
newSectionYesMarkdown body of the new section to insert. Will be wrapped under `heading` (or appended after the existing one).
targetPathYesVault-relative path of the concept or entity page to merge into. Created with canonical frontmatter if it does not exist.
citationQuoteNoOptional pull-quote from the source rendered as a blockquote under the citation.
citationSourceNoVault-relative path to a Sources/<slug>.md page. Rendered as a `[[wiki-link]]` citation under the new section and added to the page's `sources:` frontmatter list.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesThe path or identifier the tool acted on.
changedYesTrue if the tool altered vault state on this call; false if it was a no-op.
summaryYesShort human-readable summary of what happened.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.3.5
    • 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"
  2. Changed11 schema fields changedv0.3.2
    • addedInput schema / properties / aliases / description
      Added value: +"Set or replace the page's frontmatter `aliases` list."
    • addedInput schema / properties / citationQuote / description
      Added value: +"Optional pull-quote from the source rendered as a blockquote under the citation."
    • addedInput schema / properties / citationSource / description
      Added value: +"Vault-relative path to a Sources/<slug>.md page. Rendered as a `[[wiki-link]]` citation under the new section and added to the page's `sources:` frontmatter list."
    • addedInput schema / properties / entityKind / description
      Added value: +"Required only when creating a missing entity page. One of person | place | org | work | other."
    • addedInput schema / properties / heading / description
      Added value: +"H2 heading text for the new section (e.g. 'Notable Facts'). Defaults to a timestamped 'Update YYYY-MM-DD' heading."
    • addedInput schema / properties / newSection / description
      Added value: +"Markdown body of the new section to insert. Will be wrapped under `heading` (or appended after the existing one)."
    • addedInput schema / properties / pageType / description
      Added value: +"Page type used when creating a missing target page. Picks the matching frontmatter schema."
    • addedInput schema / properties / summary / description
      Added value: +"Set or replace the page's frontmatter `summary` field."
    • addedInput schema / properties / targetPath / description
      Added value: +"Vault-relative path of the concept or entity page to merge into. Created with canonical frontmatter if it does not exist."
    • addedInput schema / properties / vaultPath / description
      Added value: +"Per-call vault override."
    • addedInput schema / properties / wikiRoot / description
      Added value: +"Per-call wiki directory override."
  3. Changed4 schema fields changedv0.1.2
    • 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."
  4. First observedv0.1.0

TDQS

A4.8/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 burden of behavioral disclosure. It details what happens on both existing pages (section insertion, sources list update, `updated:` frontmatter bumped to today, summary/aliases set) and new pages (canonical frontmatter, entityKind requirement). It also explains the vault override hierarchy and the rendering of citations and quotes. Nothing is left opaque.

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?

The description is longer than minimal but every sentence carries information: purpose, conditional behavior, sibling distinction, vault handling, and two illustrative examples. It is front-loaded with the core action and usage guidance. Slightly verbose relative to the high-calibration example, but appropriate for an 11-parameter tool with nuanced merge semantics.

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?

For a tool of this complexity, the description covers the full decision space: when to use vs. alternatives, required/optional parameters, defaults, side effects on frontmatter, vault overrides, and entityKind constraints. The examples make the expected JSON shape concrete. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema: it explains that `citationSource` pushes onto the page's `sources:` frontmatter list, that `heading` defaults to a timestamped value, and how `vaultPath` overrides the session-active vault. The two examples also illustrate realistic parameter combinations, adding practical nuance.

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 opens with a precise action verb ('Add a cited section') and names the exact resources (`Concepts/` or `Entities/` pages) plus the conditional create behavior. It distinguishes itself from the sibling `wiki.ingest` by stating that this tool targets existing pages, whereas ingest handles new sources. That makes selection unambiguous.

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?

Explicit when-to-use guidance is present: 'Use this when filing a follow-up onto a known page; use `wiki.ingest` instead when bringing in a NEW source'. It also describes the vault selection behavior and notes when `entityKind` is required. This is more than adequate routing.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bezata/kObsidian'

If you have feedback or need assistance with the MCP directory API, please join our Discord server