Skip to main content
Glama

SRIFT

by app.srift
OverviewDiscussionsAdmin

Get Session Status

srift_session_status
Read-onlyIdempotent

Get current session details: session { id, role (host/guest), connection state, your userId }, pending join requests (approve with srift_approve_join), and members with their userIds (remove one with srift_kick_user).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionNoThe active session (id is null when there is none)
peerCountNoNumber of connected sockets in the room (hosted endpoint)
participantsNoSession members: pass userId to srift_kick_user to remove one
pendingJoinsNoList of pending guest join requests waiting for host approval

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / participants / description
      Previous value: -"Session members (local daemon): pass userId to srift_kick_user to remove one"New value: +"Session members: pass userId to srift_kick_user to remove one"
  2. Changed6 schema fields changed
    • removedOutput schema / properties / isConnected
      Removed value: -{
-  "description": "True if connected to signaling server",
-  "type": "boolean"
-}
    • addedOutput schema / properties / participants
      Added value: +{
+  "description": "Session members (local daemon): pass userId to srift_kick_user to remove one",
+  "items": {
+    "properties": {
+      "isHost": {
+        "type": "boolean"
+      },
+      "online": {
+        "type": "boolean"
+      },
+      "userId": {
+        "type": "string"
+      },
+      "username": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / peerCount / description
      Previous value: -"Number of connected peers in the room"New value: +"Number of connected sockets in the room (hosted endpoint)"
    • removedOutput schema / properties / role
      Removed value: -{
-  "description": "Active role: \"host\", \"guest\", or null",
-  "type": "string"
-}
    • addedOutput schema / properties / session
      Added value: +{
+  "description": "The active session (id is null when there is none)",
+  "properties": {
+    "id": {
+      "description": "Active session ID",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "isConnected": {
+      "description": "True if connected to the signaling server",
+      "type": "boolean"
+    },
+    "name": {
+      "description": "Session name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "role": {
+      "description": "\"host\", \"guest\", or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Guest only: \"pending_approval\" or \"approved\" (hosted endpoint)",
+      "type": "string"
+    },
+    "userId": {
+      "description": "Your user id in the session",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
    • removedOutput schema / properties / sessionId
      Removed value: -{
-  "description": "Active session ID, if any",
-  "type": "string"
-}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "isConnected": {
+      "description": "True if connected to signaling server",
+      "type": "boolean"
+    },
+    "peerCount": {
+      "description": "Number of connected peers in the room",
+      "type": "number"
+    },
+    "pendingJoins": {
+      "description": "List of pending guest join requests waiting for host approval",
+      "items": {
+        "properties": {
+          "tempUserId": {
+            "description": "Temporary ID of requesting user",
+            "type": "string"
+          },
+          "username": {
+            "description": "Username of requesting user",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "role": {
+      "description": "Active role: \"host\", \"guest\", or null",
+      "type": "string"
+    },
+    "sessionId": {
+      "description": "Active session ID, if any",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and non-openWorld, so the safety profile is covered. The description adds useful substance beyond that by naming the role values (host/guest), the connection-state field, and the fact that pending requests and member userIds are returned together in one payload.

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?

A single front-loaded sentence with the verb first, followed by a structured enumeration of the returned groups. No filler, no restatement of the title, and every clause conveys distinct content.

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 input parameters, a rich annotation set, and an output schema that carries the actual return shape, the description supplies everything the agent still needs: what the payload groups are and which sibling tools act on them.

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, so there is nothing for the description to disambiguate; per the baseline, a 4 is appropriate. No parameter-related claims are made or needed.

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 ('Get') and resource ('current session details') and then enumerates the exact payload: session id, role, connection state, userId, pending join requests, and members. It also names the sibling tools that act on those sub-resources, so an agent can separate this read-only snapshot from srift_approve_join or srift_kick_user.

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 clarifies the agent's context for using it ('current session details') and routes follow-up work explicitly, e.g. approve pending join requests with srift_approve_join and remove a member with srift_kick_user. It gives no explicit when-not-to-use or exclusion, so it stops short of a 5.

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