Skip to main content
Glama
Sign In
@saihm/mcp-server-pro

@saihm/mcp-server-pro

Official
by SAIHM-Admin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Join SAIHM (activate free memory)

saihm_join

Activate free SAIHM persistent memory for this agent. Call this when the user asks to join, sign up for, or set up SAIHM.

Instructions

Activate free SAIHM persistent memory for this agent. Call this when the user asks to join, sign up for, or set up SAIHM. Where no identity is configured, a join creates a NEW, EMPTY memory, so the first call answers with a question instead: whether they already have a SAIHM identity (from another machine or an earlier session). Put it to them once; if they do, do not join: they bring it with export-identity instead. In a hosted or cloud session that starts fresh each time, or in a CI job, do not join there either: they join on their own computer, then bring that identity in the same way. Once they confirm they want a new one here, call again with newIdentity: true. It self-generates a sovereign memory key on this device and starts a one-time human approval — the tool returns a URL and short code for the user to open and enter. After the user approves, the join finishes by itself and the memory tools work; there is no need to call saihm_join again. No payment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "saihm_join"
  }
}

Input Schema

NameRequiredDescriptionDefault
newIdentityNotrue once the user confirms they have no SAIHM identity to bring here and want a new, empty memory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • addedInput schema / properties / newIdentity
      Added value: +{
+  "description": "true once the user confirms they have no SAIHM identity to bring here and want a new, empty memory",
+  "type": "boolean"
+}
  2. First observedv0.2.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses key behavior: the first call may return a question rather than joining, a new join creates an empty memory and self-generates a sovereign key, a one-time human approval is started via URL and short code, and the process completes automatically without another saihm_join call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the activation purpose and then walks through the conditional flow in a structured way. It is somewhat verbose, but most of the length is justified by the multi-step identity and approval process.

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 the tool's complexity, lack of an output schema, and the important conditional paths around existing identities and hosted sessions, the description provides enough context for an agent to invoke it correctly. It covers prerequisites, side effects, and post-approval behavior.

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?

The input schema already has 100% coverage for the single newIdentity parameter, including a description. The tool description reinforces when to set it true but adds little semantic detail beyond the schema's own explanation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: activating free SAIHM persistent memory for the agent. It distinguishes this from bringing an existing identity via export-identity, but it does not explicitly differentiate among the listed sibling tools such as saihm_status, saihm_recall, or saihm_remember.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: user asks to join, sign up, or set up SAIHM. It also states when not to join, covering users with an existing identity and hosted/CI sessions, and specifies the alternative path in each case.

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