mcp-workspace

List notes

notes_list

Read-only

List Markdown notes in a workspace folder, sorted by path, with title, size, and modification time so you can inventory available notes.

Instructions

List the Markdown notes in the workspace (at most 500), sorted by path, with their title, size and modification time.

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

Input Schema

Name	Required	Description	Default
`folder`	No	Only notes under this folder

Output Schema

Name	Required	Description	Default
`notes`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive, and closed-world, so the safety burden is low. The description still adds real behavioral facts beyond them: a hard 500-result ceiling, deterministic path ordering, and the field set returned — all of which affect how an agent should handle results.

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?

One sentence, front-loaded with the verb and resource, then the quantitative scope and ordering. No filler or restated title beyond what the sentence needs.

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?

Output schema is present and annotations are rich, so return-shape and safety disclosure are unnecessary here. The remaining gap is the recursive-vs-flat semantics of the folder filter and truncation behavior past 500 notes, which the description leaves unaddressed.

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?

Single optional parameter with 100% schema description coverage ('Only notes under this folder'), so the schema carries the definition. The description adds nothing further about the folder parameter — notably it does not say whether subfolders are included recursively, which is the one ambiguity worth resolving.

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?

Specific verb (List) plus resource (Markdown notes in the workspace) with concrete scope details: 500-item cap, sorted by path, and returned fields. It doesn't explicitly contrast with notes_search or notes_read, so an agent must infer that enumeration-without-query is this tool's job from the name alone.

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?

Usage is only implied: the mention of a folder filter and the read-only listing framing suggest fetching everything or a folder subtree. No sentence says when to prefer this over notes_search, nor what to do if the 500 limit is hit.

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

Deploy Server