Skip to main content
Glama
cubicecho

RAGDown

by cubicecho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Write a note

ragdown_remember

Preserve decisions, fixes, or how-tos as a new searchable Markdown note with immediate indexing. Supersede old notes to exclude them from search results.

Instructions

Save something worth keeping (a decision, a fix, a how-to) as a new Markdown note in the notes folder, indexed immediately so later searches find it. Never overwrites an existing file. When this note replaces an earlier one, pass that note's path as supersedes so searches stop returning the old version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFile name under the notes folder, without .md; defaults to <date>-<title-slug>
tagsNo
titleYes
contentYesMarkdown body; the title and date go in frontmatter
session_idNoStable id of the conversation, recorded in the note's frontmatter
supersedesNoPaths of notes this one replaces, as returned by ragdown_recall. They stay on disk and ragdown_read_doc still opens them, but search and hook context skip them. Use it when a fact changed, not when you are merely writing about the same topic.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.0.0
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Stable id of the conversation, recorded in the note's frontmatter",
+  "type": "string"
+}
    • addedInput schema / properties / supersedes
      Added value: +{
+  "description": "Paths of notes this one replaces, as returned by ragdown_recall. They stay on disk and ragdown_read_doc still opens them, but search and hook context skip them. Use it when a fact changed, not when you are merely writing about the same topic.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the sparse annotations by disclosing indexing behavior, the non-overwrite guarantee, and that superseded notes remain readable but are excluded from search/context. Adds nuanced guidance on when to use supersedes versus merely writing about the same topic.

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?

Three sentences, each with a distinct job: core action, safety guarantee, supersede guidance. No filler or repetition of schema details.

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

Completeness4/5

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

Strong on behavior and parameter intent; slightly lacking an explicit statement of return value or generated file path, though that is derivable from naming defaults. Overall sufficient for correct invocation.

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?

The description adds important meaning to supersedes (search/context skipping, paths from ragdown_recall) and complements the schema's 67% coverage. It explains the note-save workflow but does not elaborate on less critical params like tags/title beyond what the schema provides.

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 precise action: saving durable knowledge as a new Markdown note in the notes folder, with key qualifiers 'never overwrites' and 'indexed immediately'. The verb-resource pair clearly distinguishes it from read/search siblings like ragdown_read_doc and ragdown_recall.

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

Usage Guidelines4/5

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

Gives clear conditions for use: saving decisions, fixes, how-tos, and when replacing an earlier note with supersedes. It does not explicitly contrast with read-only siblings, but the write/read split is evident from sibling names and context.

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