obsidian-modified-mcp-server

Overview Schema Source Related Servers Discussions Admin

get_recent_periodic_notes

Retrieve the most recent periodic notes for a specified period type (daily, weekly, monthly, quarterly, yearly). Optionally set a limit to control how many notes are returned.

Instructions

Get most recent periodic notes for a specified period type.

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": {
      "period": "<period>"
    },
    "name": "get_recent_periodic_notes"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of notes to return (default: 5).
`period`	Yes	The period type.
`vaultId`	No	Optional vault ID (defaults to configured default vault).
`include_content`	No	Whether to include note content (default: false).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jul 31, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention the default limit, whether content is included by default, ordering behavior, or what happens when no notes are found. The description is too sparse to convey these important behavioral traits.

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, concise sentence that is front-loaded with the action and resource. It contains no unnecessary words or repetition, making it highly efficient.

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 4 parameters, no output schema, and no annotations, the description is insufficiently complete. It does not explain the return format, default behavior, or how the tool differs from related tools. Agents may not know what 'recent' means or whether metadata vs content is returned.

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 baseline is 3. The description does not add meaning beyond the schema; the mention of 'specified period type' merely echoes the 'period' parameter. It does not clarify the semantics of 'most recent' or how 'limit' and 'include_content' interact.

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 the tool's function: 'Get most recent periodic notes for a specified period type.' The verb 'Get' and the resource 'most recent periodic notes' are specific. It distinguishes from sibling 'get_periodic_note' by indicating multiple recent notes rather than 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 Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as 'get_periodic_note' or 'search'. It merely states what it does, leaving the agent without explicit context on when this tool is the appropriate choice or any exclusions.

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