Skip to main content
Glama

obsidian_read_note

Reads a full Obsidian note by relative vault path and separates its YAML frontmatter from the Markdown body for downstream processing.

Instructions

Lit et extrait le contenu complet d'une note Obsidian avec séparation du frontmatter YAML

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": {
      "relative_path": "<relative_path>"
    },
    "name": "obsidian_read_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
relative_pathYesChemin relatif depuis la racine du coffre (ex: '01 - Projets/Repo-Doctor.md')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses a behavioral trait beyond the name: the content is returned with YAML frontmatter separated, which tells the agent to expect two logical parts. However, it says nothing about error behavior for a missing path, encoding, or whether the note is read-only (implied only by "lit").

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?

A single compact sentence that front-loads the verb and resource with no wasted clauses. It is efficient, though extremely terse for a tool with no annotations to fall back on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema and no annotations, the description covers the essential action and mentions frontmatter splitting. It leaves gaps on missing-file behavior and the exact shape of the returned content, which matter more given the absence of structured hints.

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 coverage is 100% and there is only one parameter, and the schema description already explains the relative path format with an example. The description adds no further semantics, so the baseline of 3 applies with the schema doing the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb pair ("lit et extrait") and resource ("note Obsidian") plus scope ("contenu complet", "frontmatter YAML"), so an agent knows exactly what it returns. It stops short of distinguishing itself from siblings such as obsidian_search_notes or obsidian_get_moc, so it is clear but not sibling-differentiated.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternative tool is mentioned. An agent must infer that this is the tool for fetching one note by path rather than searching, which is plausible but not stated.

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