Skip to main content
Glama
SAIHM-Admin

saihm-mcp-server (standards client)

by SAIHM-Admin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Remember

saihm_remember

Store facts, decisions, or context to encrypted persistent memory so agents retain information across sessions.

Instructions

Store information to SAIHM persistent encrypted memory. Use this when an agent or user wants a fact, decision, or piece of context to persist across sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesInformation to remember

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNo
epochNo
cellIdYes
feeNcotiNo
cellNonceNo
kekVersionNo
signaturePrefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.10
    • changedOutput schema / required
      Previous value: -[
-  "cellId",
-  "cellNonce",
-  "tier",
-  "kekVersion",
-  "epoch",
-  "feeNcoti",
-  "signaturePrefix"
-]New value: +[
+  "cellId"
+]
  2. Changed1 schema field changedv0.3.6
    • 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"
+}
  3. Changed1 schema field changedv0.3.1
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

Description adds 'persistent encrypted memory' beyond annotations, but does not detail side effects, overwrite behavior, or limitations. With annotations already indicating non-read-only and non-idempotent, the description adds moderate value.

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?

Two concise sentences with no wasted words. Front-loaded with the action and immediately useful for an agent.

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 a simple storage tool with one parameter, the description covers the main purpose and usage context. Could mention output or limits, but overall adequate given the tool's simplicity.

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 coverage is 100% and describes the single parameter 'content' as 'Information to remember'. Description does not add additional meaning beyond that, so baseline 3 is appropriate.

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?

Clearly states the verb 'Store' and resource 'SAIHM persistent encrypted memory'. Description distinguishes from sibling tools like saihm_recall and saihm_forget by emphasizing persistence across sessions.

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?

Provides explicit when-to-use context: 'when an agent or user wants a fact, decision, or piece of context to persist across sessions.' While it doesn't explicitly state when not to use, the sibling tool names make alternatives obvious.

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