Skip to main content
Glama

hjarni

by com.hjarni
OverviewDiscussionsAdmin

notes-list

Read-onlyIdempotent

List and browse the user's saved notes — their stored knowledge and memories (preferences, workflows, projects, meeting notes, references, and the rest) — with optional filtering, sorting, and pagination. Use search instead when hunting for a topic or keyword; use this to enumerate a folder, tag, or scope. Returns paginated results as a JSON array, followed by a line stating how many notes matched in total and whether more pages remain — read it to know if you have the whole folder before acting on it. Optional: team_id (integer) to list team notes, scope ('active'|'archived'|'inbox'|'favorited'|'trashed'), container_id (integer) with include_nested (boolean), tags (array of strings, AND logic), tag_ids (array of integers, AND logic), summary_stale (boolean, filter to notes with outdated summaries), stale (boolean, filter to notes whose freshness is stale — past their review_after date or unverified for a while), sort ('recent'|'oldest'|'title'), page (integer, default 1), per_page (integer, max 100, default 25), include_body (boolean, default false — include each note's full body, so a scoped/paginated listing can retrieve complete contents without a notes-get call per note; withheld for trashed notes, same as notes-get), include_instructions (boolean, defaults to include_body — include each note's inherited_instructions, the same chain notes-get returns, so a full-body listing also carries the rules governing those notes; withheld for trashed notes). container_id can be combined with team_id to list a specific team container. Example: list ruby-tagged notes in a container: {container_id: 5, tags: ['ruby']}.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
sortNoSort order: 'recent' (updated_at desc, default), 'oldest' (updated_at asc), or 'title' (alphabetical)
tagsNoFilter to notes with ALL these tags by name (AND logic). Example: ['ruby', 'rails']
scopeNoFilter scope (default: active). 'inbox' and 'favorited' only for personal notes; 'trashed' lists the recoverable Trash — restore an entry with notes-restore.
staleNoFilter to notes whose freshness is stale — past their review_after date or unverified beyond the freshness window (default: not filtered)
tag_idsNoFilter to notes with ALL these tags by ID (AND logic)
team_idNoList notes in this team instead of personal notes. Omit it (or send null) for personal notes.
per_pageNoResults per page, max 100 (default: 25)
container_idNoFilter by container ID
include_bodyNoInclude each note's full body in the results (default: false)
summary_staleNoFilter to notes with outdated summaries (default: not filtered)
include_nestedNoInclude notes from sub-containers when container_id is set (default: false)
include_instructionsNoInclude inherited_instructions (brain, space root, ancestor and container instruction layers, outermost first) on each note — the same chain notes-get returns. Defaults to the value of include_body, so full-body listings carry their governing instructions unless you pass false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / team_id / description
      Previous value: -"List notes in this team instead of personal notes"New value: +"List notes in this team instead of personal notes. Omit it (or send null) for personal notes."
    • changedInput schema / properties / team_id / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / include_body
      Added value: +{
+  "description": "Include each note's full body in the results (default: false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / include_instructions
      Added value: +{
+  "description": "Include inherited_instructions (brain, space root, ancestor and container instruction layers, outermost first) on each note — the same chain notes-get returns. Defaults to the value of include_body, so full-body listings carry their governing instructions unless you pass false.",
+  "type": "boolean"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / scope / description
      Previous value: -"Filter scope (default: active). 'inbox' and 'favorited' only for personal notes."New value: +"Filter scope (default: active). 'inbox' and 'favorited' only for personal notes; 'trashed' lists the recoverable Trash — restore an entry with notes-restore."
    • changedInput schema / properties / scope / enum
      Previous value: -[
-  "active",
-  "archived",
-  "inbox",
-  "favorited"
-]New value: +[
+  "active",
+  "archived",
+  "inbox",
+  "favorited",
+  "trashed"
+]
  4. Changed1 schema field changed
    • addedInput schema / properties / stale
      Added value: +{
+  "description": "Filter to notes whose freshness is stale — past their review_after date or unverified beyond the freshness window (default: not filtered)",
+  "type": "boolean"
+}
  5. Changed1 schema field changed
    • addedInput schema / properties / summary_stale
      Added value: +{
+  "description": "Filter to notes with outdated summaries (default: not filtered)",
+  "type": "boolean"
+}
  6. Changed2 schema fields changed
    • removedInput schema / properties / tag
      Removed value: -{
-  "description": "Filter by tag name",
-  "type": "string"
-}
    • changedInput schema / properties / tags / description
      Previous value: -"Filter to notes with ALL these tags by name (AND logic)"New value: +"Filter to notes with ALL these tags by name (AND logic). Example: ['ruby', 'rails']"
  7. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Adds substantial context beyond the read-only annotations: it explains paginated return format, the trailing count/more-pages line, and the fact that body and instructions are withheld for trashed notes. It also clarifies stale/freshness semantics and include_instructions inheritance, with no contradiction of annotations.

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?

The description is front-loaded with purpose, alternative, and return behavior, and nearly every detail is useful for a 13-parameter tool. However, the long dense 'Optional:' sentence could be more readable if structured, so it falls short of ideal concision.

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?

Given 13 optional parameters, no output schema, and read-only annotations, the description is complete enough to call the tool correctly. It covers filtering, sorting, pagination, return shape, and the main parameter interactions.

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

Parameters5/5

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

Schema coverage is 100%, but the description still adds meaningful semantics beyond the schema, such as container_id combinable with team_id, tags/tag_ids AND logic, include_body avoiding per-note notes-get calls, and include_instructions defaulting to include_body. It also provides a concrete example.

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 specific verb and resource: list and browse the user's saved notes, including examples of note content. It explicitly distinguishes this enumeration tool from search, so an agent can choose correctly without opening sibling schemas.

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 when-to-use guidance: use search for topic or keyword hunting, use this to enumerate a folder, tag, or scope. This directly names the alternative and the condition that selects it.

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

All hjarni toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources