Skip to main content
Glama
bezata

kObsidian MCP

Read Note

notes.read
Read-onlyIdempotent

Retrieve a note's body, frontmatter metadata, and statistics such as word counts and links from an Obsidian vault by providing its path. Select which sections to include for efficient access.

Instructions

Read a note and return any combination of its body, parsed frontmatter metadata, and lightweight statistics. include selects which sections to return — default is ['content', 'metadata']. Ask for ['stats'] alone when you only need word/character/heading/link/task counts and want to skip loading the full body. Read-only. Fails with not_found when path does not exist.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesVault-relative note path.
includeNoWhich sections to return. `content` = full body; `metadata` = parsed frontmatter and basic info; `stats` = word count, character count, heading count, link count, task count. Omit to get content + metadata.
vaultPathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
contentNo
metadataNo
statsNo
Behavior4/5

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

Discloses behavior beyond annotations: default sections, error on missing path, vault resolution logic. Annotations already cover safety and idempotency; description adds return format and error handling.

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?

Two concise paragraphs, no wasted words. Front-loaded with purpose and key behavior. Every sentence adds value.

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?

Complete given output schema exists and tool is straightforward. Covers purpose, parameter behavior, error case, and vault context. No gaps.

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?

Adds meaning beyond schema for `include` (default and stats tip) and `vaultPath` (precedence rule). Schema coverage is 67%, but description compensates 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?

Clear verb 'read' and resource 'note', with explicit mention of returnable sections (body, frontmatter, stats). Differentiates from siblings like notes.list, notes.edit, and notes.search by emphasizing read-only and vault context.

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

Usage Guidelines4/5

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

Provides concrete usage advice for the `include` parameter (default value, stats-only tip) and error behavior. Mentions vault context and `vaultPath` precedence. Lacks explicit comparison to sibling tools for when to use this vs alternatives.

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