mcp-vault-reader

vault_list_notes

List notes in your vault with optional filters for folder, tag, and result limit to quickly find relevant notes.

Instructions

Lists notes in a specific vault, with optional filters for subfolders, specific tags, and a limit on the number of results.

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": {
      "vault_name": "<vault_name>"
    },
    "name": "vault_list_notes"
  }
}

Input Schema

Name	Required	Description
`tag`	No	Optional tag (without '#') to filter notes.
`limit`	No	Optional limit for the number of notes returned.
`folder`	No	Optional subfolder relative path to filter notes.
`vault_name`	Yes	The name of the vault.
`response_format`	No	Format of the response: 'text' (default) or 'json'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read-only listing operation but does not mention important behaviors such as default limit if no limit is specified, sorting order, exact match vs partial match for tags, or whether the return includes full note content or just metadata. This leaves agents uncertain about edge cases.

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 a single sentence that is direct and information-dense. It front-loads the core purpose and mentions key optional filters without extraneous words.

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 tool has no output schema and no annotations, the description is insufficiently complete. It does not clarify what the returned list contains (note titles, paths, or content), whether vault_name must exist, or how filters combine. These are significant gaps for an agent to invoke the tool correctly without additional assumptions.

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 description coverage is 100%, so the schema already fully documents the parameters. The description adds little beyond paraphrasing the filter and limit parameters, and does not provide extra meaning such as default values, syntax examples, or parameter interactions.

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 a specific action (Lists notes) and a specific resource (in a specific vault), and mentions optional filters for subfolders, tags, and limit. This distinguishes it from sibling tools like vault_search (likely full-text search) and vault_read_note (read a single note).

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?

The description implies usage for listing and filtering notes within a vault, but does not explicitly state when to use this tool versus alternatives like vault_search or vault_get_related. It provides context (filters, limit) but no explicit exclusions or when-not-to-use guidance.

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

Deploy Server