Skip to main content
Glama

List notes

list_notes
Read-onlyIdempotent

Retrieve notes in most recently updated order, optionally filtered by tag, and paginate results with offset or next_offset for browsing a personal knowledge base.

Instructions

List notes, most recently updated first. Paginate with offset / next_offset.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOnly notes with this tag
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
notesYes
totalYesNumber of notes matching the filter
next_offsetNoPass as offset to get the next page; null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so safety is covered. The description adds two genuinely behavioral facts beyond that: results are sorted by most-recent update, and traversal is via offset / next_offset. It still omits whether a total count is returned or how many pages exist.

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, scoping and ordering front-loaded, pagination second. Nothing is redundant and nothing could be cut without losing information.

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 described, and the tool is a simple three-parameter read. Still, an agent gets no guidance on the tag filter, the 100-item limit ceiling, or how this differs from search_notes, which matters for correct tool selection.

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 only 33%, but the description only clarifies offset (paginate via offset / next_offset) and references next_offset, which is an output field rather than an input. The tag filter and, critically, the limit cap of 100 receive no added meaning beyond 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?

The description states a specific verb and resource ("List notes") and adds ordering ("most recently updated first"), so it is clearly a plain enumeration tool rather than a lookup. It never names a sibling like search_notes or get_note, so differentiation must be inferred from the verb alone.

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 or when-not-to-use guidance: nothing says whether to use this for browsing all notes versus search_notes for filtered queries, nor when the tag filter is preferable. The pagination remark is operational, not a usage rule.

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