vault-memory

Overview Schema Source Related Servers Discussions Admin

search_text

Read-onlyIdempotent

Find exact words or phrases in Obsidian notes using BM25 full-text search, with optional vault filters and result limits.

Instructions

Full-text BM25 search via SQLite FTS5. Best for exact-word and phrase matches.

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_text"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes
`top_k`	No
`vaults`	No
`exclude_paths`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0-rc.5May 29, 2026

TDQS

B3.2/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 only implementation flavor (BM25 via FTS5); it says nothing about result ordering, scoring, or behavior with empty/no matches beyond what annotations provide.

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 short sentences, no waste, with the core purpose and the differentiator front-loaded. Nothing could be trimmed without losing signal.

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?

For a four-parameter search tool with no output schema and zero schema descriptions, the two-sentence description leaves top_k, vaults, and exclude_paths entirely unexplained. An agent cannot know how to scope the search or how many results it will get.

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?

Schema description coverage is 0% and the description explains none of the four parameters. 'Query' is inferable from 'full-text search', but top_k, vaults, and exclude_paths are completely undocumented in both the schema and the description, so the tool fails to compensate for the coverage gap.

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 (full-text search) plus the underlying mechanism (SQLite FTS5), and 'exact-word and phrase matches' implicitly distinguishes it from the semantic/hybrid siblings. It stops short of naming those alternatives outright, so sibling differentiation is only implied.

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?

'Best for exact-word and phrase matches' gives a usage signal that helps an agent pick between this and search_semantic/search_hybrid. However, it never names those alternatives or states when NOT to use it, leaving the routing decision to inference.

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