Skip to main content
Glama
Sign In
notes-mcp

notes-mcp

by gabed5303-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_recent_notes

Read-only

Retrieve a list of the most recently created or updated notes, sorted newest first. Returns summaries for quick scanning; fetch full content separately.

Instructions

List the most recently created or updated notes, newest first.

    Returns summaries — fetch a full note with get_note.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of notes to return.

Output Schema

NameRequiredDescriptionDefault
countYesNumber of notes returned.
notesYesNotes ordered by last update, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already mark readOnlyHint=true. The description adds that it returns summaries and suggests get_note for full notes, but no additional behavioral traits like pagination or auth needs.

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?

Two concise lines with no fluff. First line states purpose, second adds useful context about summaries and alternative.

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 list tool with 1 parameter and output schema, the description covers essentials. Minor gap: no mention of summary format, but overall sufficient.

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 clear description for limit parameter. The description provides no additional meaning beyond the schema.

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 verb (list), resource (recent notes), and ordering (newest first). It distinguishes from siblings like search_notes and get_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 using get_note for full content but does not explicitly when to use this versus alternatives like search_notes. No exclusion criteria.

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