Skip to main content
Glama
SAIHM-Admin

saihm-mcp-server (standards client)

by SAIHM-Admin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Recall

saihm_recall
Read-onlyIdempotent

Retrieve stored memories from an encrypted memory store. Enter a keyword to filter results, or leave empty to load all past context at session start.

Instructions

Retrieve memories from the SAIHM encrypted store; the operator decrypts and returns plaintext, this client holds no keys. Use this 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
NameRequiredDescriptionDefault
queryNoFilter by keyword (empty = all)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
memoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.10
    • changedOutput schema / properties / memories / items / required
      Previous value: -[
-  "cellId",
-  "kekVersion",
-  "cellNonce",
-  "timestamp",
-  "tier",
-  "plaintext"
-]New value: +[
+  "cellId",
+  "plaintext"
+]
  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": {
+    "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"
+}
  3. Changed1 schema field changedv0.3.1
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observedv0.1.2

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. The description adds useful context beyond those: the client holds no keys, an external operator performs decryption, and an empty query loads all memories. No contradiction with 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?

Two sentences, each earning its place: the first states the action and security model, the second covers when to use it and how the parameter behaves. There is no filler or redundant boilerplate.

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 tool with one optional parameter, an output schema, and safety annotations, the description covers purpose, timing, empty-query behavior, and the key-handling model. Nothing an agent needs to invoke it correctly is missing.

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 the query parameter is already described as 'Filter by keyword (empty = all)'. The description restates that behavior without adding new format, example, or edge-case detail, so the schema carries the load.

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 opens with a specific verb-and-resource claim ('Retrieve memories from the SAIHM encrypted store') and immediately clarifies that an operator decrypts and returns plaintext. This clearly distinguishes it from sibling tools like saihm_remember, saihm_forget, and saihm_status.

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?

It gives an explicit trigger: 'Use this at the start of a session or whenever past context is needed.' It does not explicitly enumerate exclusions or name alternatives, but the usage context is clear and not misleading.

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