Skip to main content
Glama
anpigon

Obsidian Omnisearch MCP Server

by anpigon

obsidian_notes_search

Search your Obsidian vault for notes matching a query and retrieve their absolute file paths for further access.

Instructions

Search Obsidian(옵시디언) notes and return absolute paths to the matching notes. The returned paths can be used with the read_note tool to view the note contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • The handler function for the 'obsidian_notes_search' tool. It searches Obsidian notes using a local HTTP endpoint at localhost:51361, sorts results by score, and formats them with title, excerpt, score, and absolute filepath. Registered via @mcp.tool() decorator.
    @mcp.tool()
    def obsidian_notes_search(query: str):
        """Search Obsidian(옵시디언) notes and return absolute paths to the matching notes.
        The returned paths can be used with the read_note tool to view the note contents.
        """
        try:
            search_url: str = "http://localhost:51361/search?q={query}"
            response = requests.get(search_url.format(query=quote(query)))
            response.raise_for_status()  # Raise an exception for bad status codes
            json_response = response.json()
            sorted_results = sorted(
                json_response, key=lambda x: x["score"], reverse=True
            )
            return [
                f"<title>{item['basename']}</title>\n"
                f"<excerpt>{item['excerpt']}</excerpt>\n"
                f"<score>{item['score']}</score>\n"
                f"<filepath>{os.path.join(obsidian_vault_path, item['path'].lstrip('/'))}</filepath>"
                for item in sorted_results
            ]
    
        except Exception:
            return []
  • Registers the obsidian_notes_search tool using FastMCP's @mcp.tool() decorator.
    @mcp.tool()
  • Input schema defined by function signature (query: str) and docstring description.
    def obsidian_notes_search(query: str):
        """Search Obsidian(옵시디언) notes and return absolute paths to the matching notes.
        The returned paths can be used with the read_note tool to view the note contents.
        """
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 of behavioral disclosure. It describes the action (search) and output (absolute paths), but lacks details on behavioral traits such as search scope (e.g., full-text, metadata), performance (e.g., speed, limits), error handling, or authentication needs. This is a significant gap for a tool with no 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 appropriately sized and front-loaded: two sentences that directly state the tool's purpose and usage. Every sentence earns its place by providing essential information without waste, making it efficient and easy to understand.

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 (a search tool with no output schema and no annotations), the description is incomplete. It explains the basic purpose and output format but lacks critical context such as search behavior, result limitations, error cases, or integration details with the sibling tool. This leaves gaps for an AI agent to understand how to use it effectively.

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

Parameters2/5

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

The input schema has 1 parameter ('query') with 0% description coverage, meaning the schema provides no details about it. The description does not add any semantic information about the 'query' parameter, such as its format, syntax, or examples. This leaves the parameter largely undocumented, failing to compensate for the low schema coverage.

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 tool's purpose: 'Search Obsidian notes and return absolute paths to the matching notes.' It specifies the verb (search), resource (Obsidian notes), and output (absolute paths). However, it does not explicitly differentiate from its sibling 'read_note' beyond mentioning that the returned paths can be used with it, which is more of a usage hint than a distinction.

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 provides clear context for usage: 'The returned paths can be used with the read_note tool to view the note contents.' This indicates when to use this tool (to find notes) versus its sibling (to read them). However, it lacks explicit exclusions or alternatives, such as when not to use it or if there are other search methods.

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

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