Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Read Note

notes.read
Read-onlyIdempotent

Read a note from an Obsidian vault, returning its body, frontmatter metadata, and optional stats. Specify which sections to retrieve—content, metadata, or counts—to get only what you need.

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
statsNo
contentNo
metadataNo

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. Changed8 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / include
      Added value: +{
+  "default": [
+    "content",
+    "metadata"
+  ],
+  "description": "Which 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.",
+  "items": {
+    "enum": [
+      "content",
+      "metadata",
+      "stats"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / path / description
      Added value: +"Vault-relative note path."
    • addedOutput schema / properties / content
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / metadata
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / path
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / stats
      Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "characters": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "headings": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "links": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "tasks": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "words": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / required
      Added value: +[
+  "path"
+]
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses the `not_found` error on missing paths and explains the vault selection behavior (session-active vault vs. explicit vaultPath). This adds meaningful operational context that the annotations do not cover.

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 compact and well-organized. The first sentence states the purpose and options; the second gives practical usage guidance; the third clarifies vault context. Every sentence earns its place without redundant information.

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 read tool with an output schema, the description covers the essential aspects: return sections, error behavior, vault selection, and parameter semantics. No critical information for correct invocation is missing.

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 enriches the `include` parameter with explanation of what each value returns and the default, and clarifies `vaultPath` precedence. Since schema coverage is 67%, the description compensates for the undocumented `vaultPath` and adds nuance beyond the schema's enum for `include`.

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 reads a note and returns selected sections (body, metadata, stats). It specifies the resource (note) and action (read), and the mention of the `include` parameter distinguishes it from listing/searching tools. This is specific and unambiguous.

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?

It gives clear context for when to use this tool (reading a specific note by path) and even provides guidance on using `include` to request stats only. However, it does not explicitly name alternative sibling tools or state when not to use it, so it falls short of the 'explicit when/when-not/alternatives' criterion.

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