Skip to main content
Glama

list_recent

List recently changed notes in an Obsidian vault, newest first, to review recent activity and identify what has changed.

Instructions

The n notes changed most recently, latest first. A quick way to see what has been happening in the vault.

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

Input Schema

NameRequiredDescriptionDefault
nNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the ordering guarantee (latest first) and that results are scoped to changed notes, which are genuinely useful behavioral facts; however it does not say whether "changed" includes newly created notes, whether content or only metadata is returned, or anything about permissions.

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 short sentences with zero filler, and the core behavior plus ordering is front-loaded before the optional framing sentence.

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?

An output schema exists, so return structure needn't be described, and the tool is a simple one-parameter read. The description covers purpose, ordering, and the count parameter; only the ambiguous definition of "changed" is a residual gap.

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%, but with a single parameter the description fully explains its meaning: "n notes" tells the agent it is a count controlling result size, and the ordering sentence clarifies it caps the recency window. Only the default of 10 is left to the schema, which is appropriate.

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 resource and ordering: the n most recently changed notes, latest first. An agent can distinguish this recency listing from query_notes or search_brain by the description alone, though it never names those siblings explicitly.

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?

"A quick way to see what has been happening in the vault" implies a monitoring/overview use case, but there is no explicit when-to-use versus when-to-use-something-else guidance, no named alternative for targeted lookups, and no exclusions.

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