Skip to main content
Glama
bezata

kObsidian MCP

Merge Summary Into Concept Or Entity Page

wiki.summaryMerge

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

Output Schema

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

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

No annotations provided, so the description carries the full burden. It states side effects like bumping 'updated:' frontmatter, adding citation to sources list, and creating pages with canonical frontmatter. However, it does not clarify behavior when a heading already exists or if duplicate citation handling occurs.

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 well-structured with a clear first paragraph, usage guidelines, and examples. It is front-loaded but slightly lengthy; could be tightened without losing clarity.

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 the tool's complexity (11 parameters, 2 required) and the presence of an output schema, the description covers creation, merging, citation, frontmatter updates, and vault selection completely.

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?

The description adds significant meaning beyond the 100% schema coverage. It explains default heading behavior, citation mechanics, entityKind requirement, and provides examples that illustrate parameter usage effectively.

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 clearly states the tool adds a cited section to existing concept/entity pages or creates the page if missing. It also distinguishes from sibling 'wiki.ingest' by specifying when to use each.

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 explicitly says when to use this tool (filing follow-up on known page) and when to use 'wiki.ingest' instead (new source). It also notes that 'entityKind' is required when creating a new entity page, and explains vault behavior.

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

Install Server

Other Tools

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