Another bloated Obsidian MCP Server

by diegorv

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

list_daily_notes

List daily notes from an Obsidian vault, filtered by start and end dates, with an optional limit on results.

Instructions

List daily notes, optionally filtered by date range

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_daily_notes"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of notes to return (default: 30)
`endDate`	No	End date in YYYY-MM-DD format
`startDate`	No	Start date in YYYY-MM-DD format

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It only mentions optional date filtering, but does not describe sorting, pagination, return format, or what constitutes a daily note. 'List' implies read-only, but lacks critical context for an agent to anticipate behavior.

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 one concise sentence that front-loads the primary action and optional filter. It contains no redundant words or filler, achieving high clarity in minimal space.

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?

Since there is no output schema and no annotations, the description should explain return values and behavioral details. It does not mention what the response contains, ordering, or limits beyond the schema default. For a listing tool, this leaves significant gaps for an agent.

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 already documented. The description adds only 'optionally filtered by date range', which largely duplicates schema information and provides no additional semantic value.

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 uses a specific verb 'List' and a resource 'daily notes', which clearly distinguishes it from siblings like get_daily_note (singular), create_daily_note, and append_to_daily. The optional date range filter is also explicitly mentioned, making the purpose unambiguous.

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 daily notes but provides no explicit guidance on when to use it over alternatives like list_notes or get_daily_note. Sibling names offer context, but the description itself does not state exclusions or alternatives, so guidance is only implied.

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