Skip to main content
Glama

obsidian_search_notes

Read-onlyIdempotent

Search an Obsidian vault by note name or content to return matching notes with snippets and obsidian:// links.

Instructions

Search the vault by note name and content; returns matches with snippets and obsidian:// links.

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": "obsidian_search_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
vault_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine value by disclosing the return shape (matches with snippets and obsidian:// links), but says nothing about vault resolution, authentication, or result limits.

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?

A single front-loaded sentence with no filler; the search scope and return shape are both stated efficiently.

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 simple two-parameter read-only search with no output schema, the description covers the search behavior and return format adequately. The main gap is the unexplained vault_path parameter, which matters if multiple vaults exist.

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 0% schema description coverage, the description must carry parameter meaning. It clarifies that query matches note name and content, but leaves vault_path completely unexplained, so only one of two parameters is covered.

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?

States a specific verb and resource ('Search the vault') and scopes it to note name and content, so an agent can tell it is a search operation rather than a read or list. It does not explicitly differentiate from nearby siblings like obsidian_list_notes or obsidian_read_note, keeping it short of a 5.

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?

Usage is implied by the word 'Search' and the vault scope, but the description never says when to prefer this over obsidian_list_notes or to follow up with obsidian_read_note. No explicit exclusions or alternatives are given.

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