saihm-mcp-server (standards client)

Recall

saihm_recall

Read-onlyIdempotent

Retrieve past memories from an encrypted store to restore context at session start or when needed. Filter by keyword, or leave empty to load all.

Instructions

Retrieve memories from the SAIHM encrypted store; the operator decrypts and returns plaintext, and this client holds no keys. Use at the start of a session, or whenever past context is needed. Pass a keyword to filter, or leave empty to load all.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Filter by keyword (empty = all)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`memories`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.10Jul 29, 2026

changedOutput schema / properties / memories / items / required

Previous value: -[
-  "cellId",
-  "kekVersion",
-  "cellNonce",
-  "timestamp",
-  "tier",
-  "plaintext"
-]New value: +[
+  "cellId",
+  "plaintext"
+]

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": {
+    "count": {
+      "type": "number"
+    },
+    "memories": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "cellId": {
+            "type": "string"
+          },
+          "cellNonce": {
+            "type": "string"
+          },
+          "kekVersion": {
+            "type": "string"
+          },
+          "plaintext": {
+            "type": "string"
+          },
+          "tier": {
+            "type": "string"
+          },
+          "timestamp": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "cellId",
+          "kekVersion",
+          "cellNonce",
+          "timestamp",
+          "tier",
+          "plaintext"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "memories"
+  ],
+  "type": "object"
+}

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

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so safety and mutation behavior are covered. The description adds meaningful context beyond annotations: the operator performs decryption and the client holds no keys. This clarifies an important architectural behavior without contradicting the annotations.

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 concise sentences cover purpose, usage context, and parameter behavior. The description is front-loaded with the core action and wastes no words on irrelevant detail.

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 simple tool with one optional parameter, rich annotations, and an output schema, the description is complete. It states what the tool does, when to use it, how to control scope with the query parameter, and a key security-relevant behavioral detail about key handling.

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 single query parameter is documented as "Filter by keyword (empty = all)." The description restates this guidance almost exactly without adding new semantic information, so it meets the baseline but does not exceed it.

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 clearly identifies the operation: "Retrieve memories from the SAIHM encrypted store." It also distinguishes this from sibling tools like saihm_remember and saihm_forget by focusing on retrieval of stored context. The added detail about operator decryption and plaintext return makes the purpose even more concrete.

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 provides explicit timing guidance: "Use at the start of a session, or whenever past context is needed." It does not explicitly name alternatives or state when not to use it, but the usage context is clear enough for an agent to select it appropriately among siblings.

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

Deploy Server