Skip to main content
Glama
LamantinAI

kaeru memory

by LamantinAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

episode

Create a named operational memory you can recall by exact name; optionally share it to the cloud or link it to an existing node in one call.

Instructions

Write a deliberately-named operational episode. Use when you know you'll want to recall by exact name. Pass visibility=shared (in a team initiative) to capture and push to the cloud in one call. Pass link_to (with weight) to connect it to an existing node in this same call — an island is found only by exact name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesFree-form body.
nameYesShort, recallable name.
afterNoOptional: hold this back until `after` (YYYY-MM-DD), then surface it in `awake` as a debt. For something TRUE LATER, NOT NOW — a certificate that expires, a number to re-measure before quoting it again, work to pick up after the next release. Requires `for_days`.
cloudNoWhich cloud `visibility=shared` publishes to. Only consulted when sharing. Required when several clouds are configured — the push is refused rather than sent to a default you did not name.
layerNoOptional memory layer stamped at creation: `core`, `hot`, `warm`, `cold`, or `frozen`. Defaults to `warm`.
weightNoHow load-bearing the `link_to` edge is, 0..1. REQUIRED with `link_to`: it is the only signal knowledge chains route on, and there is no default because an unweighted graph makes every chain rank on noise. The capture still lands without it; the edge does not.
link_toNoOptional: the node this one connects to, by name or id — the edge is made in THIS call, while both ends are still in mind. Linking as a second step is the step nobody takes: one real vault reached 23 nodes and 0 edges with the nudge asking every time. Needs `weight`.
for_daysNoOptional: how many days the reminder keeps appearing once it surfaces. REQUIRED with `after`, and there is no default — state it deliberately, because "the certificate expires" and "re-measure this" want completely different windows. The window starts when the reminder is first actually seen, so it cannot expire while nobody is looking.
edge_typeNoEdge type for `link_to` — same closed vocabulary as `link` (`refers_to` by default, `causal`, `derived_from`, `contradicts`, `part_of`, `blocks`, `targets`, `supersedes`, `verifies`, `falsifies`, `temporal`, `consolidated_to`).
initiativeNo
visibilityNoOptional visibility. `shared` marks team knowledge and — in a `team` initiative with the secret guard clear — pushes it to the cloud in this one call. Defaults to `local` (stays private).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful side effects: visibility=shared pushes to the cloud in the same call, link_to creates an edge immediately, and orphaned captures are only retrievable by exact name. It does not cover permissions, reversibility, or failure modes, so it is good but not complete.

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?

Four sentences, front-loaded with purpose and usage, and each carries an actionable instruction. The exact-name point is stated twice (once for recall, once for linking), which is mild redundancy keeping it from a 5.

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?

For an 11-parameter write tool with 91% schema coverage and no output schema, the description adequately frames the core workflow (named capture, optional cloud push, optional inline edge). Remaining gaps around non-core parameters are covered by the schema, so nothing critical is missing.

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?

Schema coverage is already 91%, so the baseline is 3; the description adds real meaning on top by clarifying the link_to/weight coupling and by implying that `name` is the exact-match recall key. It does not explain most parameters (after, layer, edge_type, cloud), leaving the schema to do that work.

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 deliberately-named operational episode") and adds a differentiating qualifier: it is the capture path for content you will later find by exact name. This is clearly distinct from generic capture siblings, though no sibling tool is named explicitly for contrast.

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 a clear when-to-use trigger ("Use when you know you'll want to recall by exact name") and two conditional workflows (visibility=shared for team/cloud, link_to for edge creation in the same call). No explicit exclusions or named alternatives, so it falls short of a 5.

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