@saihm/mcp-server-pro

Official

by SAIHM-Admin

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Status

saihm_status

Read-onlyIdempotent

Check the active session to view agent identity, tier, custody mode, shard and sharing counts, and bfsi score—without exposing plaintext.

Instructions

Show the current SAIHM session: the agent identity, which this client derives locally, plus the tier, custody mode, shard and sharing counts, and bfsi score the server reports. No plaintext appears, because the server holds none. Use it to check which identity is active and what is stored and shared.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`bfsi`	No
`tier`	No
`error`	No
`timing`	No
`custody`	No
`features`	No
`agentIdHash`	No
`snapshotEpoch`	No
`activeShardCount`	No
`seqStateDegraded`	No
`activeSharingContracts`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.13.0Oct 7, 2026

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "status": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "code",
+    "status"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / features

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "warmStart": {
+          "anyOf": [
+            {
+              "additionalProperties": {},
+              "properties": {
+                "token": {
+                  "const": "required",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            {
+              "items": {},
+              "type": "array"
+            },
+            {
+              "type": "string"
+            },
+            {
+              "type": "number"
+            },
+            {
+              "type": "boolean"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / timing

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "admission": {
+      "anyOf": [
+        {
+          "enum": [
+            "reserved",
+            "shared"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "serverMs": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "totalMs": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "serverMs",
+    "totalMs",
+    "admission"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "agentIdHash",
-  "tier",
-  "custody",
-  "activeShardCount",
-  "activeSharingContracts",
-  "bfsi",
-  "snapshotEpoch",
-  "seqStateDegraded"
-]

Changed5 schema fields changedv0.2.2Aug 31, 2026

changedOutput schema / properties / activeShardCount / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedOutput schema / properties / activeSharingContracts / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedOutput schema / properties / bfsi / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

addedOutput schema / properties / seqStateDegraded

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "agentIdHash",
-  "tier",
-  "custody",
-  "activeShardCount",
-  "activeSharingContracts",
-  "bfsi",
-  "snapshotEpoch"
-]New value: +[
+  "agentIdHash",
+  "tier",
+  "custody",
+  "activeShardCount",
+  "activeSharingContracts",
+  "bfsi",
+  "snapshotEpoch",
+  "seqStateDegraded"
+]

First observedv0.2.1Jul 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare the safe read profile (readOnly, idempotent, non-destructive). The description adds genuinely non-obvious behavior: the identity is derived locally by the client, and no plaintext appears because the server holds none. That privacy/architecture context is real value beyond the structured fields, though it omits any session prerequisites.

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 tight sentences, front-loaded with the verb and the returned fields, followed by the privacy note and the use case. No filler or repetition.

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?

An output schema exists, so return values need not be explained, and the description covers scope, data handling, and usage. The only omission is whether a session must first be established (e.g. via saihm_join) before the status is meaningful.

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 tool takes zero parameters, which is the baseline-4 case. The schema is empty and fully covered, so there is nothing further the description needs to specify.

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?

States a precise verb+resource ('Show the current SAIHM session') and enumerates exactly what is returned: agent identity, tier, custody mode, shard and sharing counts, and bfsi score. It is unmistakably distinct from the write-oriented siblings (remember, forget, share, revoke_share).

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?

'Use it to check which identity is active and what is stored and shared' gives a clear triggering context, so the agent knows when to reach for it. It stops short of naming alternatives or when-not conditions, but for a status read that is a small gap.

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

Deploy Server