Skip to main content
Glama
SAIHM-Admin

@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: first ask whether they already have a SAIHM identity (from another machine or an earlier session) - if so, do not join; they bring it with export-identity instead. In a hosted or cloud session that starts fresh each time, do not join there either: they join on a machine they keep, then bring that identity in the same way. Pass newIdentity: true once they confirm they want a new one here. 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.

Input Schema

TableJSON 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.6/5.0
Behavior5/5

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

Annotations only declare the mutation/idempotency/open-world profile; the description adds substantive behavior: it self-generates a sovereign memory key on-device, triggers a one-time human approval returning a URL and short code, completes asynchronously without a second call, and involves no payment. This is exactly the extra context annotations cannot carry.

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?

Front-loaded with the core action, then branches into the two do-not-join cases and the approval mechanics. Well organized, though 'the join finishes by itself' and 'there is no need to call saihm_join again' are mildly redundant.

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?

With no output schema, the description covers the return value (URL plus short code), the post-approval state (memory tools work), and the no-payment guarantee. An agent has everything needed to call this correctly and to tell the user what to expect.

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 single parameter's schema description already spells out the confirmation precondition. The description's 'Pass newIdentity: true once they confirm' restates rather than extends the schema, so the baseline 3 applies.

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 specific verb and resource: 'Activate free SAIHM persistent memory for this agent.' It is immediately distinguishable from siblings like saihm_remember, saihm_recall, and saihm_status, which operate on an existing memory rather than creating one.

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?

Explicit when-to-use ('when the user asks to join, sign up for, or set up SAIHM') and explicit when-not-to-use with alternatives: ask about an existing identity first and route to export-identity, and do not join in fresh hosted/cloud sessions. This is unusually complete routing guidance.

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