Skip to main content
Glama
rex

mcp-apple-obsidian

by rex
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

obsidian_search_notes

Search notes in an Obsidian vault using text queries or regex patterns, with options for case sensitivity and content search.

Instructions

Search for notes containing specific text or matching a pattern.

Args:
    vault: Name or path of the vault
    query: Search query (supports regex patterns)
    case_sensitive: Whether search is case sensitive
    search_content: Whether to search in file content (not just names)
    
Returns:
    JSON array of matching notes with context

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vaultYes
queryYes
case_sensitiveNo
search_contentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses search in content and names, regex support, and returns a JSON array with context, but lacks details about pagination, limits, or edge-case behavior.

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?

Front-loaded purpose, followed by args and returns. Clear structure with minimal redundancy, though could be slightly more concise.

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 the number of sibling tools and no output schema provided, the description covers core behavior adequately but omits details about default sorting, result limits, and vault validation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description adds meaningful details for all four parameters (vault, query, case_sensitive, search_content) and explains regex support, fully compensating for schema gaps.

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 searches for notes by text or pattern, which distinguishes it from sibling tools like obsidian_find_notes_by_tag or obsidian_search_by_property.

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?

No explicit guidance on when to use this tool vs alternatives. It implies usage for text search but does not set boundaries or mention exclusions.

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/rex/mcp-apple-obsidian'

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