Skip to main content
Glama

list_pages

Read-onlyIdempotent

Lists all Markdown pages in a vault with their titles, optionally limited to a subfolder, to help you review and navigate notes.

Instructions

List every Markdown page in the vault with its title.

Args: folder: Optional subfolder to list, relative to the vault root (for example "lca").

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

Input Schema

NameRequiredDescriptionDefault
folderNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description needn't restate it. The description adds that the listing is exhaustive ("every Markdown page"), but leaves two behavioral questions open: whether a folder listing recurses into nested subfolders, and whether large vaults are truncated or paginated.

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 front-loaded sentence states the scope and the payload, followed by a single docstring-style arg note; there is no filler and nothing is buried. The arg description is placed after the purpose, which is the right order for a scan-then-parse read.

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?

An output schema exists, so return values need not be explained, and the annotations cover the safety semantics. For a whole-vault enumeration tool, however, the definition is silent on scale behavior (pagination/truncation), recursion depth under folder, and result ordering – gaps an agent would want closed before calling it on a large vault.

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

Parameters4/5

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

Schema coverage is 0% – the schema only declares folder as a string with an empty default – so the description carries the full burden and largely meets it: it marks folder optional, says it is relative to the vault root, and gives a concrete example ("lca"). What it does not say is whether the path is matched recursively or only at the top level.

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?

"List every Markdown page in the vault with its title" gives a specific verb (list), a specific resource (Markdown pages in the vault), and states what comes back (titles). It is clearly distinguishable from read_page and search, but it does so implicitly rather than by naming them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says to prefer this over search when you want a complete inventory, nor any condition for when a full listing is inappropriate. The optional folder arg is the only hint that this is a scoped enumeration, so an agent must infer the choice of tool from the verb alone.

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