NoteDiscovery MCP Server

get_recent_notes

Find what you were working on recently by retrieving notes modified in the last N days. Set the limit to control how many are returned.

Instructions

Get recently modified notes. Useful for finding what you were working on recently.

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": "get_recent_notes"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Get notes modified in the last N days (default: 7)
`limit`	No	Maximum number of notes to return (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 24, 2026

TDQS

A3.9/5.0

Behavior3/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. It states a read operation ('Get...') but does not disclose ordering (e.g., by modification time descending), return format fields, or any side effects. The behavior is simple but could be more explicit.

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 at two sentences with no wasted words. It is front-loaded with the core function and immediately gives a usage hint.

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 simplicity and good schema coverage, the description is nearly complete, but it lacks details about the return format (e.g., fields, sorting). This is a minor gap for a list tool without an output schema.

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 coverage is 100% with descriptions for both 'days' and 'limit' parameters. The description adds no extra meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 'Get recently modified notes', specifying a distinct verb and resource. Compared to sibling tools like get_note (single note), get_notes_by_tag, and search_notes, this tool's purpose is uniquely identified by the recency criterion.

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

Usage Guidelines4/5

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

The description provides a clear usage context: 'Useful for finding what you were working on recently.' It implies appropriate use cases but does not explicitly mention when not to use or suggest alternatives like get_notes_by_tag for tag-based queries.

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