Renor

note

Stores a memory entry by appending text to a dated daily journal, defaulting to today, so agents can retain context across sessions.

Instructions

Store a memory entry in the daily notes. Appends text to the daily note for the given date.

Input Schema

Name	Required	Description
`date`	No	Date in YYYY-MM-DD format (defaults to today)
`text`	Yes	Text to remember
`source`	No	Ignored. The author is this connection's header-form name, or mcp when the connection has no usable name. Never a file path or document name.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`path`	Yes
`detail`	No
`warning`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.3.0Oct 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "detail": {
+      "type": "string"
+    },
+    "ok": {
+      "const": true,
+      "type": "boolean"
+    },
+    "path": {
+      "type": "string"
+    },
+    "warning": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "path"
+  ],
+  "type": "object"
+}

First observedv1.2.0Oct 28, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does communicate the key trait that this is additive (append, not overwrite). It omits whether a missing note file is created, whether repeated calls duplicate text, and any auth or rate-limit context.

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?

Two short sentences, front-loaded with the action. There is mild redundancy between 'Store a memory entry in the daily notes' and 'Appends text to the daily note', but nothing extraneous follows.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and all three parameters are documented in-schema. Still, for a mutation tool with zero annotations, the description should state side effects such as note creation and duplicate handling; its absence leaves a real gap.

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 description coverage is 100% and the schema already explains the date format, default-to-today behavior, and the unusual ignored 'source' parameter. The description only echoes 'given date' and adds nothing beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

The description states a specific verb and resource: it appends text to the daily note for a given date. That is clearly distinct from a generic write, but it never distinguishes this append-a-journal-entry behavior from siblings like remember_fact or facts, which serve overlapping memory-storage purposes.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool instead of remember_fact, entity, or evidence, and no exclusions. An agent choosing among six memory-related siblings gets no routing signal.

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

Deploy Server