Datacron

Overview Schema Source Related Servers Discussions Admin

Create memory note

create_note_ai

Records durable facts, decisions, and preferences as typed Markdown memory notes. Use it proactively to preserve context and log rejected options.

Instructions

Call this proactively when a durable fact, confirmed decision, or user preference emerges in conversation - do not wait to be asked. Skip speculation and one-off chatter. Write a new typed _memory Markdown note. Use rejected entries in 'option -- reason' format to record discarded options so a future agent does not propose them again. This is a write operation: it is confined to DATACRON_WRITE_PATHS, never overwrites existing files, writes a durable operation record, and relies on the MCP client's tool approval for human-in-the-loop review.

Input Schema

Name	Required	Description	Default
`body`	Yes
`tags`	Yes
`title`	Yes
`origin`	Yes
`rejected`	No
`rel_path`	Yes
`confidence`	Yes
`request_id`	No
`supersedes`	No
`last_verified`	No

Output Schema

Name	Required	Description	Default
`created`	No
`indexed`	Yes
`rel_path`	No
`replayed`	No
`committed`	No
`content_hash`	Yes
`operation_id`	No
`organization`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.1.17Oct 17, 2026
- addedOutput schema / description
```
Added value: +"Successful ``create_note_ai`` payload."
```
- removedOutput schema / properties / committed / default
```
Removed value: -null
```
- removedOutput schema / properties / created / default
```
Removed value: -null
```
- removedOutput schema / properties / operation_id / default
```
Removed value: -null
```
- removedOutput schema / properties / organization / default
```
Removed value: -null
```
- removedOutput schema / properties / rel_path / default
```
Removed value: -null
```
- removedOutput schema / properties / replayed / default
```
Removed value: -null
```

Changed1 schema field changedv0.1.16Oct 1, 2026

addedOutput schema / properties / organization

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Organization"
+}

Changed1 schema field changedv0.1.13Sep 23, 2026

removedInput schema / properties / expected_hash

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Expected Hash"
-}

Changed9 schema fields changedv0.1.5Sep 5, 2026

addedInput schema / properties / request_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Request Id"
+}

addedOutput schema / properties / committed

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Committed"
+}

removedOutput schema / properties / created / $ref
```
Removed value: -"#/$defs/CreatedNoteOutput"
```

addedOutput schema / properties / created / anyOf

Added value: +[
+  {
+    "$ref": "#/$defs/CreatedNoteOutput"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / created / default
```
Added value: +null
```

addedOutput schema / properties / operation_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Operation Id"
+}

addedOutput schema / properties / rel_path

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Rel Path"
+}

addedOutput schema / properties / replayed

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Replayed"
+}

changedOutput schema / required

Previous value: -[
-  "created",
-  "content_hash",
-  "indexed"
-]New value: +[
+  "content_hash",
+  "indexed"
+]

First observedv0.1.0Jul 31, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Annotations already declare the write/safety profile, yet the description adds substantial context: confinement to DATACRON_WRITE_PATHS, no overwriting of existing files, creation of a durable operation record, and reliance on client tool approval for human review. This is genuinely useful behavioral disclosure beyond the structured hints.

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 the proactive-call guidance, then the note type, then the write semantics, so the most decision-relevant content comes first. It is dense and mostly waste-free, though the final sentence is a long multi-clause run-on.

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?

An output schema exists, so return values need not be explained, and the write semantics and scope constraints are covered well. The gap is parameter documentation, which is largely absent given the 10-parameter, 0%-coverage schema, but behaviorally the definition is nearly complete.

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

Parameters2/5

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

Schema description coverage is 0% across 10 parameters, so the description carries the full burden. It only adds meaning for the 'rejected' parameter (the 'option -- reason' format); rel_path, title, body, origin, confidence, tags, supersedes, last_verified, and request_id are left entirely undocumented in both places.

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?

States a specific verb and resource: 'Write a new typed _memory Markdown note,' which an agent can distinguish from search/get/patch siblings. It does not, however, explicitly name which sibling to use instead (e.g., append_journal) in adjacent scenarios, so it falls short of full sibling differentiation.

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 explicit triggering conditions ('when a durable fact, confirmed decision, or user preference emerges') and clear exclusions ('skip speculation and one-off chatter'), plus a proactive-call directive. It stops short of naming alternative tools for the excluded cases, so it is strong but not a 5.

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