Skip to main content
Glama
everton-dgn

vault-search-mcp

by everton-dgn

search_advanced

Run semantic search with structured filters, combining optional filters like tags, folder, dates, and status to retrieve matching notes.

Instructions

Run semantic search with structured filters.

Every optional filter is combined with AND.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNotag filter, with OR between tags
queryYessemantic search text
top_kNonumber of results
folderNofolder filter including descendants
statusNonote status
date_toNoISO end date, ignored when date_range is set
excludeNoterms to exclude from results
projectNoassociated project name
categoryNocategory
date_fromNoISO start date, ignored when date_range is set
extensionNofile extension such as md, canvas, or pdf
highlightNohighlight query terms in result text
note_typeNonote type
date_rangeNotoday, week, month, or year

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
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 disclosing behavioral traits. 'Run semantic search' implies a read-only query, but the description does not explicitly state that it performs no side effects, does not mutate data, or is safe to invoke. The behavior is not fully transparent.

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 extremely concise, consisting of two short sentences. It communicates the essential operation and filter combination rule without unnecessary words, padding, or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (14 parameters) and lack of annotations, the description is somewhat thin. It does not mention expected output behavior, result ordering, or interaction with sibling search tools. The schema parameters are well described, so the missing pieces are mostly contextual guidance rather than parameter-level details.

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?

The schema description coverage is 100%, with each parameter having a description. The main description adds a useful semantic that all optional filters are combined with AND, which clarifies interaction between parameters. However, it does not go beyond the schema to explain nuanced behaviors like date_range precedence or exclusion semantics in more depth.

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 states a clear action: 'Run semantic search with structured filters.' It identifies the resource (semantic search) and mentions structured filtering, making the core purpose understandable. However, it does not explicitly distinguish itself from sibling search tools like search_vault_hybrid or search_vault, so it is not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool instead of alternative search tools. The sentence 'Every optional filter is combined with AND' describes filter behavior but does not help the agent decide between this and sibling tools. This leaves usage decisions under-specified.

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