Skip to main content
Glama
Sign In

SRIFT

by app.srift
OverviewDiscussionsAdmin

Join SRIFT Session

srift_join_session

Request to join an existing SRIFT session by its 7-character session ID. The host must approve before transfers/chat work.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sessionId": "<sessionId>"
    },
    "name": "srift_join_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameNoDisplay name (optional, defaults to AI-Agent)
sessionIdYes7-character session ID (e.g. ABC1234)
roomSecretNoOptional shared secret matching the host's

Output Schema

NameRequiredDescriptionDefault
statusNoJoin request status (approved, pending, or joined)
messageNoStatus message or instructions
sessionIdYesSession room code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "message": {
+      "description": "Status message or instructions",
+      "type": "string"
+    },
+    "sessionId": {
+      "description": "Session room code",
+      "type": "string"
+    },
+    "status": {
+      "description": "Join request status (approved, pending, or joined)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "sessionId"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations mark it as non-read-only, non-idempotent, and open-world, and the description usefully adds the approval-gate behavior that structured fields cannot convey. It does not describe the failure/pending state or what the agent should do while awaiting approval, keeping it below a 5.

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 tight sentences with no filler; the core action is front-loaded and the approval prerequisite follows immediately.

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?

With a full output schema and full parameter coverage, the description only needs to convey the workflow role, which it does. Minor gap: it could clarify what the caller receives or should do before approval lands.

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%, so sessionId, username, and roomSecret are already documented, including defaults and an example. The description only restates the 7-character session ID constraint, adding no new semantic detail beyond 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 (request to join) and resource (an existing SRIFT session) with the identifying key (7-character session ID). It is clearly distinct from siblings like srift_approve_join, srift_start_session, and srift_reject_join.

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?

The description establishes the workflow context: the host must approve before transfers/chat work, which tells the agent this is a pending-request step rather than an immediate membership grant. It does not name alternatives (e.g., checking srift_session_status first), so it falls short of explicit when/when-not guidance.

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

All SRIFT toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources