Skip to main content
Glama

list_notes

List notes with IDs, titles, projects, and tags, optionally filtered by project or tag to find relevant Memex memory records.

Instructions

List notes (id, title, project, tags), optionally filtered by project and/or tag.

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
tagNo
limitNoDefault 50, max 100.
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It establishes that this is a read/list operation and discloses the returned fields, but says nothing about result ordering, pagination beyond the limit cap, behavior when no filter is given, or what happens when a project/tag matches nothing.

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?

A single sentence with zero filler: purpose first, returned fields in parentheses, filtering semantics last. Nothing could be removed 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?

Without an output schema, listing the returned fields is the right compensating move, and it does that. But for a list tool capped at 100 items, the absence of any pagination or ordering information leaves a real gap for an agent that may need to iterate.

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 description coverage is only 33% (only limit is documented), so the description deserves credit for explaining that project and tag act as optional filters. However, it does not clarify whether filters combine with AND or OR, or whether tag accepts a single value only.

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 notes" is a specific verb+resource, and the parenthetical (id, title, project, tags) tells the agent exactly what comes back. It separates itself from single-note siblings like read_note by being a plural list, but it never names an alternative 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?

"optionally filtered by project and/or tag" implies the intended usage pattern in a natural way, but there is no explicit when-to-use versus read_note, recall, or list_tags, and no statement of preconditions or exclusions.

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