obsidian-modified-mcp-server

Overview Schema Source Related Servers Discussions Admin

get_heading_contents

Retrieve raw markdown body content under a specific heading in an Obsidian note by providing its full heading path (e.g., H1::H2). Excludes frontmatter and metadata, giving you just the section text.

Instructions

Returns the raw markdown body content under the targeted heading. Frontmatter, tags, and file metadata are not included — use get_file_contents for the whole note or get_frontmatter_field for individual frontmatter values. Heading targets MUST use the full path of the heading: at least two non-empty segments separated by "::" (i.e., the H1::H2[::H3...] form). Top-level headings (no parent) are unreachable through this tool — use get_file_contents and slice the note client-side. Headings whose literal text contains "::" are also unreachable through this tool (the validator treats every "::" as a path separator and there is no escape syntax) — use get_file_contents in that case as well.

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": {
      "filepath": "<filepath>",
      "heading": "<heading>"
    },
    "name": "get_heading_contents"
  }
}

Input Schema

Name	Required	Description
`heading`	Yes	Full heading path: at least two non-empty segments separated by '::' (i.e., the H1::H2[::H3...] form). Top-level headings and headings whose literal text contains '::' are unreachable through this tool — fall back to get_file_contents for those cases.
`vaultId`	No	Optional vault ID (defaults to configured default vault).
`filepath`	Yes	Path to the file (relative to vault root).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jul 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden. It discloses the return content (raw markdown body), exclusions (frontmatter, tags, metadata), path constraints, and unreachable cases. This is comprehensive behavioral transparency.

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 somewhat long but well-structured, front-loading the action and then providing exclusions and constraints. Every sentence adds value, though the 'unreachable' cases could be slightly more compact. It is appropriately sized for the tool's complexity.

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 with significant behavioral constraints (heading path format, unreachable top-level headings, literal '::' limitations), the description covers all necessary context. It explains what is returned, what is excluded, and exactly when to use alternatives. The absence of an output schema is acceptable since the return type (raw markdown body) is implicitly clear.

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 the baseline is 3. The description reinforces the heading format and adds context about when to use fallbacks, but it does not add meaning beyond what the schema already provides. It meets the baseline without exceeding it.

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's function: 'Returns the raw markdown body content under the targeted heading.' It also explicitly differentiates from sibling tools like get_file_contents (whole note) and get_frontmatter_field (frontmatter values), making the purpose 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?

The description provides explicit when-to-use guidance, including exclusions: top-level headings and headings containing '::' are unreachable, with direct fallback instructions to get_file_contents. This is outstanding usage guidance.

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