Skip to main content
Glama
sunub

Obsidian MCP Server

Obsidian Content Getter

vault

Search and retrieve content from Markdown documents in your Obsidian vault to find notes, synthesize information, and answer questions based on saved records.

Instructions

Retrieves and searches the content of Markdown (.md, .mdx) documents stored in an Obsidian vault. Use this tool to find notes related to a specific topic or keyword and understand their core content.

When to use:

  • When you need to find a specific note by its title or a keyword to check its content.

  • When you want to synthesize and summarize information scattered across multiple notes.

  • When looking for answers to questions based on your saved records, such as "What was the project deadline?"

  • To discover connections by finding all notes that link to a specific note.

  • When you need to retrieve a list of unfinished tasks (- [ ]) from daily notes or meeting minutes.

Returns the content of the most relevant document(s) in text format. It can also include metadata such as the document's title, tags, and creation date.

Requirements: The user's Obsidian Vault path must be correctly configured in an environment variable or a similar setting. For searches, use the exact filename or include core keywords for content-based queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe action to perform: search documents, read specific file, list all content, or get stats
keywordNoKeyword to search for in documents (required for search action)
filenameNoSpecific filename to read (required for read action)
limitNoMaximum number of results to return (default: 10 for search, unlimited for others)
includeContentNoWhether to include document content in search results (default: true)
includeFrontmatterNoWhether to include frontmatter metadata in results (default: false)
excerptLengthNoLength of content excerpt to include in search results (default: 500)
quietNoIf true, suppresses non-error output messages. Default is false.
Behavior4/5

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

The description adds valuable behavioral context beyond the openWorldHint annotation. It explains what the tool returns ('content of the most relevant document(s) in text format'), includes metadata details, and specifies configuration requirements. However, it doesn't mention performance characteristics like search speed or result ranking algorithms.

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 clear sections and front-loaded purpose statement. Each sentence serves a purpose, though the 'When to use' section could be slightly more concise. Overall, it's appropriately sized for a tool with 8 parameters and no output schema.

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

Completeness4/5

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

For a read/search tool with comprehensive schema coverage and openWorldHint annotation, the description provides good context about return format, metadata, and usage scenarios. The main gap is the lack of output schema, but the description partially compensates by describing what's returned. It could benefit from more detail about error conditions or search limitations.

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?

With 100% schema description coverage, the schema already documents all 8 parameters thoroughly. The description doesn't add significant parameter-specific information beyond what's in the schema, though it mentions 'exact filename or core keywords' which relates to the keyword/filename parameters. Baseline 3 is appropriate given the comprehensive schema.

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 purpose with specific verbs ('retrieves and searches') and resources ('Markdown documents stored in an Obsidian vault'). It distinguishes from sibling tools like 'create_document_with_properties' and 'write_property' by focusing on read/search operations rather than creation or modification.

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 includes an explicit 'When to use' section with five specific scenarios, providing clear guidance on appropriate contexts. It distinguishes from sibling tools by focusing on finding, synthesizing, and retrieving existing content rather than creating or organizing new content.

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/sunub/obsidian-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server