Skip to main content
Glama

List Notes

list_notes
Read-onlyIdempotent

Check the user's saved notes before answering when their request refers to something they told you earlier, asks what they noted or decided, or would benefit from a running list they keep (packing lists, ideas, decisions, todos). Returns each note's id, title, content preview, and agent_access ("collaborate" or "read_only" — you may only append to or update the ones set to collaborate), newest first. Optional q filters by a case-insensitive match on title and body; optional source narrows to notes a given client authored ("me" = the user's own web edits). Private to the account; read-only.

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
qNoCase-insensitive substring match on note title and content.
limitNoMaximum number of notes to return (1–50). Default: 20.
offsetNoNumber of notes to skip for pagination. Default: 0.
sourceNoNarrow to notes from one origin: "me" for web edits (no source), "agent" for any MCP/client-authored note, or a client name for an exact match.

Output Schema

NameRequiredDescriptionDefault
countYes
notesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is known. The description earns credit for real added context — result ordering, the agent_access permission split ('you may only append to or update the ones set to collaborate'), and account-level privacy — but that extra detail was largely folded into the purpose sentence rather than developed as behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger condition before the return shape, and nearly every clause carries information (permission rule, ordering, filter semantics). It is dense to the point of being crowded — multiple em-dash asides and nested parentheticals in a two-sentence block — which slightly hurts scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers what an agent needs to decide and call correctly: when to check, what each result contains, ordering, permission implications of agent_access, and both filters. An output schema already documents return structure, yet the description still gives the permission-critical field semantics that the schema alone would not convey.

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 100%, so baseline is 3. The description still adds meaning: it clarifies q matches on both title and body case-insensitively, and it identifies source as the originating client with 'me' meaning the user's own web edits, which reinforces the schema's phrasing with purpose context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('Check the user's saved notes') and enumerates exactly what comes back — id, title, content preview, and agent_access — with ordering ('newest first'). The 'content preview' wording plus the list framing cleanly separates it from the single-record get_note sibling.

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

Usage Guidelines5/5

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

Gives explicit, concrete trigger conditions: the user refers to something told earlier, asks what they noted or decided, or needs a running list (packing lists, ideas, decisions, todos). It also frames this as a proactive pre-answer check rather than a passive lookup, which is unusually actionable guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.