mcp-minis

Overview Schema Source Related Servers Discussions Admin

list_notes

Retrieve notes from a vault, most recently updated first, filtering by tag or limiting results; previews help agents inspect stored knowledge.

Instructions

List notes in the vault, most recently updated first.

Args: tag: Optional — only list notes carrying this tag. limit: Maximum number of notes to return (1-100, default 20). The result always reports the total number of matching notes, so a truncated list is never mistaken for the whole vault.

Returns: A list of notes with previews, or a message if the vault is empty.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tag`	No
`limit`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.0Oct 1, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 20,
+  "title": "Limit",
+  "type": "integer"
+}

First observedv0.1.0Sep 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses sort order (most recently updated first), that the result reports the total matching count so truncation is visible, and that an empty vault returns a message. It stops short of stating permissions/auth needs, but the read-only nature is evident from 'List'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded main sentence followed by tight Args/Returns structure; every line is functional. The total-count explanation is slightly more than the minimum but earns its place by preventing truncation misreads.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-param, zero-required list tool with an output schema, the description covers ordering, filtering, result bounding, truncation disclosure and the empty case. An agent has everything needed to call it correctly without opening the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: tag is documented as an optional filter by carried tag, and limit is given a semantic bound (1-100) plus the default of 20, none of which appears in the schema.

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?

States a specific verb and resource plus ordering behavior ('List notes in the vault, most recently updated first'), which is clear. It does not, however, distinguish itself from the sibling search_notes, which could plausibly cover the tag-filtering case, so the agent must infer the boundary.

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 tag and limit args imply when to filter or bound results, and the note about totals guards against misreading a truncated list. But there is no explicit when-to-use or when-to-use-instead guidance naming alternatives like search_notes or get_note.

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

Deploy Server