saihm-mcp-server (standards client)

Status

saihm_status

Read-onlyIdempotent

Check the current session's status to verify agent identity, reputation, storage by tier, and sharing state. Shows PRS, BFSI, and PHI as reported by the operator.

Instructions

Show SAIHM session status (PRS, BFSI, storage by tier, sharing, PHI), as far as the operator reports them — a non-custodial operator cannot see stored-byte totals. Use this to check the agent identity, reputation, storage, and sharing state of the current SAIHM session.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`phi`	No
`custody`	No
`prsLevel`	No
`prsScore`	No
`bfsiScore`	No
`agentIdHash`	Yes
`snapshotEpoch`	No
`feeDiscountPct`	No
`activeShardCount`	No
`activeSharingContracts`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.10Jul 29, 2026

addedOutput schema / properties / custody
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "agentIdHash",
-  "prsScore",
-  "prsLevel",
-  "bfsiScore",
-  "feeDiscountPct",
-  "activeShardCount",
-  "activeSharingContracts",
-  "phi",
-  "snapshotEpoch"
-]New value: +[
+  "agentIdHash"
+]

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": {
+    "activeShardCount": {
+      "type": "number"
+    },
+    "activeSharingContracts": {
+      "type": "number"
+    },
+    "agentIdHash": {
+      "type": "string"
+    },
+    "bfsiScore": {
+      "type": "number"
+    },
+    "feeDiscountPct": {
+      "type": "number"
+    },
+    "phi": {
+      "type": "number"
+    },
+    "prsLevel": {
+      "type": "string"
+    },
+    "prsScore": {
+      "type": "string"
+    },
+    "snapshotEpoch": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "agentIdHash",
+    "prsScore",
+    "prsLevel",
+    "bfsiScore",
+    "feeDiscountPct",
+    "activeShardCount",
+    "activeSharingContracts",
+    "phi",
+    "snapshotEpoch"
+  ],
+  "type": "object"
+}

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?

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. Description adds value by noting that results depend on operator reporting and that non-custodial operators cannot see stored-byte totals. No contradiction.

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, front-loaded with key purpose and scope, no unnecessary words.

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?

Given zero parameters, existing annotations, and presence of output schema, the description fully covers what the tool does, its limitations, and when to use it.

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?

No parameters exist, so baseline is 4. Description adds context about what status includes, which is helpful but not required for parameter semantics.

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?

Description clearly states it shows SAIHM session status listing specific areas (PRS, BFSI, storage by tier, sharing, PHI). Verb 'Show' and resource are precise, and it distinguishes from sibling tools which have different functions.

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?

Explicitly states use case: 'check the agent identity, reputation, storage, and sharing state of the current SAIHM session.' It does not explicitly mention when not to use it, but the context and sibling tools make alternatives clear.

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

Deploy Server