Skip to main content
Glama
Sign In
Obsidian Everywhere

Obsidian Everywhere

by junnnnnw00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search Notes

search_notes
Read-onlyIdempotent

Search note content and titles, with optional tag and folder filters to narrow results.

Instructions

Full-text search over note content and titles, with optional tag/folder filters. Each result includes its outgoing/incoming link counts and tags.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoFilter to notes carrying this tag (nested tags match as a prefix).
limitNoMax results (default 10).
queryNoFull-text search query (FTS5 syntax). Omit to just filter by tag/folder.
folderNoFilter to notes under this vault-relative folder path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, so the description adds non-obvious behavioral context by noting that results include outgoing/incoming link counts and tags.

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?

Two succinct sentences, no filler, front-loaded with the core action. Every sentence earns its place.

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?

Given no output schema, description specifies result content (link counts and tags). Lacks details on sorting or pagination, but limit is in schema. Sufficient for a search tool with good annotations.

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% with detailed parameter descriptions (e.g., 'nested tags match as a prefix'), so the description adds minimal parameter-specific value beyond summarizing the filters. Baseline 3 is appropriate.

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 it performs 'full-text search over note content and titles' with optional filters, which distinguishes it from siblings like list_notes (just list) and get_notes_by_tag (filter by tag only).

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?

The description implies usage when full-text search is needed, and the distinction from other search tools (regex_search, list_notes) is clear, though it doesn't explicitly state when not to use or name alternatives.

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