Skip to main content
Glama
Sign In
mcp-vault-reader

mcp-vault-reader

by LucasRocha179
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

vault_get_daily_notes

Retrieve daily and periodic notes from an Obsidian vault with optional date filtering and count limits. Use standard YYYY-MM-DD formats to find specific entries.

Instructions

Retrieves daily/periodic notes from the vault, optionally filtered by date and limited in count. Supports typical YYYY-MM-DD formats.

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

Input Schema

NameRequiredDescriptionDefault
dateNoOptional specific date string (e.g. '2026-06-19') or partial date query.
limitNoOptional limit on the number of notes returned.
vault_nameYesThe name of the vault.
response_formatNoFormat of the response: 'text' (default) or 'json'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are present, so the description carries the burden. It discloses the date format support and optional filtering/limit behavior, but does not mention response format default, error cases, or explicitly confirm a read-only nature beyond the verb 'Retrieves'. Moderate disclosure for a simple retrieval tool.

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 two sentences, front-loaded with the main action, and contains no filler. It efficiently communicates the core purpose and key options.

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?

For a simple retrieval tool, the description covers the essential aspects: what it retrieves, optional date filter, limit, and date format. The schema handles the parameter details, and while no output schema exists, the description plus schema is sufficient for typical use. It does not explain return structure, but that is a minor gap for this complexity.

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?

All four parameters have schema descriptions (100% coverage), so the description adds minimal semantics beyond the schema. It reinforces the date format and limit concepts but does not explain vault_name or response_format beyond what the schema already provides, warranting the baseline 3.

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 verb 'Retrieves' and specifies the resource as 'daily/periodic notes', which distinguishes it from sibling tools like vault_read_note and vault_list_notes. It also notes optional date filtering and limiting, but lacks an explicit alternative comparison.

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 fetching daily/periodic notes and mentions date filtering, but does not provide explicit when-to-use versus alternatives or exclusion criteria. It offers clear context but no exclusions, so it is not fully prescriptive.

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

Deploy Server

Other Tools