Filter and list notes by tag, type, project, or related entity, returning the most recent entries first.
List notes with optional filters. Returns notes sorted by most recent first.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Filter by a single tag | |
| limit | No | ||
| note_type | No | ||
| project_id | No | Scope to one project. Defaults to SAGA_PROJECT if set, else the whole database. | |
| related_entity_id | No | ||
| related_entity_type | No |
Changes observed during successful MCP inspections.
v1.16.0Input schema / properties / project_id / descriptionPrevious value: -"Scope to one project. Needed when a single database holds several projects; defaults to the SAGA_PROJECT env var if set, otherwise the whole database."New value: +"Scope to one project. Defaults to SAGA_PROJECT if set, else the whole database."v1.10.0Input schema / properties / project_idAdded value: +{
+ "description": "Scope to one project. Needed when a single database holds several projects; defaults to the SAGA_PROJECT env var if set, otherwise the whole database.",
+ "type": "integer"
+}v1.5.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already communicate that the tool is read-only, idempotent, and non-destructive. The description adds a useful observable behavior: notes are sorted most recent first. It does not contradict the annotations, though it does not mention result limits or other runtime behaviors.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no filler. The core action is front-loaded, and the sorting behavior is stated in a second short sentence. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the basic list behavior and ordering, which is adequate for a simple read-only tool. However, with six optional parameters and no output schema, key details like available filters, default limits, and result shape are left unspecified, making the definition only partially complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With only 33% schema description coverage and six parameters, the description needed to explain filter semantics but only says 'optional filters.' It does not clarify note_type, related_entity_id/related_entity_type pairing, the SAGA_PROJECT default, or the default limit, so it provides little value beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (List) and resource (notes), and adds helpful detail about optional filtering and sorting by recency. It is easy to understand what the tool does, though it does not explicitly differentiate from the sibling note_search tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'optional filters' implies this is the appropriate tool when you need to list or filter notes, so usage is inferable. However, there is no explicit guidance about when to prefer note_search instead, nor any exclusions or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.