Skip to main content
Glama
Sign In
Obsidian MCP Server

Obsidian MCP Server

by igorilic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_notes

Find notes in your Obsidian vault by searching content, titles, tags, or specific folders to locate relevant information quickly.

Instructions

Search notes in the vault by content, tags, or folder.

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": {
      "query": "<query>"
    },
    "name": "search_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query (searches in content and titles)
tagsNoFilter by tags
folderNoLimit search to a specific folder
limitNoMaximum number of results (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions searching but doesn't disclose behavioral traits such as whether results are paginated, if the search is case-sensitive, what the return format is, or any rate limits. This is a significant gap for a search tool with zero annotation coverage.

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 a single, efficient sentence that front-loads the core purpose ('Search notes in the vault') and specifies searchable attributes. There is zero waste, and every word earns its place.

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

Completeness2/5

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

Given the complexity of a search tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., result format, pagination) and doesn't compensate for the absence of structured fields, making it inadequate for full agent understanding.

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 schema already documents all parameters (query, tags, folder, limit) with descriptions. The description adds no additional meaning beyond what's in the schema, such as search syntax or interaction between parameters. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the verb ('search') and resource ('notes in the vault'), specifying the searchable attributes ('by content, tags, or folder'). It distinguishes from siblings like 'list_recent_notes' (which lacks search) and 'find_backlinks' (which focuses on links), though it doesn't explicitly name these distinctions.

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

Usage Guidelines3/5

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

The description implies usage for searching notes based on content, tags, or folders, but doesn't explicitly state when to use this vs. alternatives like 'list_recent_notes' (for recent notes without search) or 'find_backlinks' (for link-based queries). No exclusions or prerequisites are mentioned.

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

Deploy Server

Other Tools