Skip to main content
Glama
farena-ai

Sara

by farena-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List notes

list_notes
Read-onlyIdempotent

Lists planner notes as titles and IDs, newest first or filtered by words, so you can find a note's ID before reading, updating, or deleting it. Read-only.

Instructions

List the notes in the owner's planner in Sara (titles only), newest first, or the ones matching some words. Use it to find a note's id; then read it with read_note, change it with update_note or remove it with delete_note. Returns plain text, up to 100 lines: "- #id title [project] (updated YYYY-MM-DD)", or "No notes." Read-only.

Input Schema

NameRequiredDescriptionDefault
queryNoOnly notes containing these words (title or text). Leave out to list the newest notes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • changedInput schema / properties / query / description
      Previous value: -"Only notes with these words."New value: +"Only notes containing these words (title or text). Leave out to list the newest notes."
    • addedInput schema / properties / query / examples
      Added value: +[
+  "deploy",
+  "recipe"
+]
    • addedInput schema / properties / query / maxLength
      Added value: +200
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Despite readOnlyHint already being present, it adds real behavioral context: exact return shape ('- #id title [project] (updated YYYY-MM-DD)' or 'No notes.'), a 100-line cap, and ordering (newest first). That is the kind of output-shape disclosure an agent needs before calling.

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-loads purpose, then workflow, then return format — efficient and well-ordered. The trailing 'Read-only.' slightly duplicates the readOnlyHint annotation, a minor redundancy.

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?

Single optional parameter, no output schema, and the description covers purpose, workflow, return format, and limits. Nothing material is missing for correct invocation.

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 100% and the query parameter already documents 'only notes containing these words (title or text)' with examples. The description's 'or the ones matching some words' restates the schema rather than adding syntax, limits, or matching rules, so baseline 3 applies.

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 the notes in the owner's planner'), plus scope details (titles only, newest first, optional word matching) that separate it from read_note and search siblings.

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?

Explicitly routes the agent: use it to find a note's id, then read_note, update_note, or delete_note. The primary workflow and the downstream alternatives are named rather than inferred.

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

Deploy Server

Other Tools