Skip to main content
Glama

obsidian_list_notes

Read-onlyIdempotent

Lists notes in an Obsidian vault newest first and returns obsidian:// links that open each note in the app.

Instructions

List notes in the Obsidian vault, newest first, each with an obsidian:// link that opens it in the app.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax notes to return (default 50)
folderNoOptional vault-relative folder, e.g. 'Projects'
vault_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely useful behavior: results are ordered newest first and each note carries an obsidian:// deep link. It omits pagination/cursor behavior and what happens past the default 50, which keeps it from a 5.

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 resource, then ordering, then return shape. Every clause earns its place with no restatement of the name.

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?

With no output schema, the description usefully characterizes the return value (note entries plus obsidian:// links) rather than leaving it opaque. The remaining gap is scoping mechanics — how vault_path interacts with the implicit vault and whether listing recurses into subfolders.

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 67%: limit and folder carry their own descriptions, while vault_path has none in either the schema or the description. The description offers no parameter guidance at all, so the baseline 3 applies rather than a higher mark.

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+resource ("List notes in the Obsidian vault") with the ordering and return shape stated up front. It is distinguishable from obsidian_search_notes by name alone, but the description never names that sibling to make the boundary explicit.

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?

Listing is implicitly contrasted with searching only by the plain meaning of the verb; there is no explicit 'use this to browse, use obsidian_search_notes to query' directive. An agent can infer the when, but is given no exclusions or prerequisites.

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