Skip to main content
Glama

SRIFT

by app.srift
OverviewDiscussionsAdmin

Get Session Status

srift_session_status
Read-only

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 (local daemon): 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. 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"
-}
  2. 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"
+}
  3. 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 readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful context about what the status payload contains and confirms the tool only observes state, with no side effects implied. No further behavioral caveats are needed for a no-param status read.

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?

One front-loaded sentence states the core action and then efficiently maps returned data to relevant sibling actions. No filler or redundant phrasing; every clause carries useful information.

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?

For a no-param, read-only status tool with an output schema and safe annotations, the description fully covers what to expect and what actions to take based on the returned data. Sibling references complete the workflow picture.

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 has zero parameters, so schema description coverage is 100% and there is no parameter burden to shoulder. The description correctly focuses on output rather than inputs, matching the baseline for a zero-param tool.

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'), then enumerates exact contents: session id, role, connection state, userId, pending join requests, and members with userIds. Clearly distinct from sibling action tools like srift_approve_join and 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?

Provides clear context that this is a read-only status retrieval, and explicitly routes follow-up actions to siblings (srift_approve_join for requests, srift_kick_user for members). Lacks an explicit 'use this instead of X' statement, but the action-oriented sibling references make the boundary clear.

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