saihm-mcp-server (standards client)

Remember

saihm_remember

Save facts, decisions, or context to persistent encrypted memory so they outlive the current session. Returns a cell ID for later retrieval or deletion.

Instructions

Store information in SAIHM persistent encrypted memory. Use this when a fact, decision, or piece of context should outlive the current session. Returns the cell id that saihm_forget takes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`content`	Yes	Information to remember

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tier`	No
`epoch`	No
`cellId`	Yes
`feeNcoti`	No
`cellNonce`	No
`kekVersion`	No
`signaturePrefix`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.10Jul 29, 2026

changedOutput schema / required

Previous value: -[
-  "cellId",
-  "cellNonce",
-  "tier",
-  "kekVersion",
-  "epoch",
-  "feeNcoti",
-  "signaturePrefix"
-]New value: +[
+  "cellId"
+]

Changed1 schema field changedv0.3.6Jun 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "cellId": {
+      "type": "string"
+    },
+    "cellNonce": {
+      "type": "string"
+    },
+    "epoch": {
+      "type": "string"
+    },
+    "feeNcoti": {
+      "type": "string"
+    },
+    "kekVersion": {
+      "type": "string"
+    },
+    "signaturePrefix": {
+      "type": "string"
+    },
+    "tier": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "cellId",
+    "cellNonce",
+    "tier",
+    "kekVersion",
+    "epoch",
+    "feeNcoti",
+    "signaturePrefix"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.3.1Jun 3, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv0.1.2May 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description adds context beyond annotations by revealing that the memory is persistent and encrypted, and that the tool returns a cell id usable by saihm_forget. The annotations already cover safety hints (readOnlyHint=false, destructiveHint=false), so the description's additional behavioral detail is valuable but not exhaustive.

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 short sentences with no filler. The main purpose is front-loaded, the usage guideline follows immediately, and the return value is mentioned because it directly enables the sibling forget operation.

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?

For a single-parameter write tool with an output schema and safety annotations, the description is complete. It specifies what to store, when to use it, and what it returns, including the link to saihm_forget for removal.

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 schema covers the only parameter with 'Information to remember,' and the description complements this by clarifying acceptable content types: facts, decisions, or context that should outlive the session. This adds practical meaning beyond the bare schema definition.

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?

The description states a specific verb ('Store') and resource ('SAIHM persistent encrypted memory'), making the tool's function immediately clear. It also distinguishes itself from siblings by indicating this is the write operation, while saihm_forget is the delete operation and saihm_recall is presumably the read operation.

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?

The description explicitly states when to use the tool: when a fact, decision, or piece of context should outlive the current session. It does not provide explicit when-not-to-use guidance or name alternatives, but the use case is clear and sufficient for this simple tool.

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

Deploy Server