SRIFT

Get Session Status

srift_session_status

Read-only

Get current session details: id, role (host/guest), connection state, pending join requests, peer count.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`role`	No	Active role: "host", "guest", or null
`peerCount`	No	Number of connected peers in the room
`sessionId`	No	Active session ID, if any
`isConnected`	No	True if connected to signaling server
`pendingJoins`	No	List of pending guest join requests waiting for host approval

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 8, 2026

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"
+}

First observedSep 8, 2026

TDQS

A4.1/5.0

Behavior3/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 a list of returned fields but no additional behavioral context, such as behavior when no session is active or whether the status is live vs. cached. This is adequate given the annotations, but the description itself contributes little beyond output semantics.

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 sentence that leads with the action and resource, followed by a concise field list. Every word earns its place; no filler, redundancy, or unnecessary background.

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 parameterless, read-only status tool with an output schema, the description is complete. The output schema handles return-value structure and the annotations handle safety; the description tells the agent exactly what information is available. No critical gap remains.

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 input schema has zero parameters, so there is nothing to describe on the input side. Per the baseline for 0-parameter tools, the description appropriately focuses on the returned session details rather than inputs.

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?

The description uses a specific verb ('Get') and resource ('current session details') and enumerates the exact fields returned (id, role, connection state, pending join requests, peer count). This clearly differentiates it from sibling tools that start, close, join, approve, or reject sessions, leaving no ambiguity about what the tool does.

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

Usage Guidelines3/5

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

The description makes it implicitly clear this is the read-only status getter among the sibling action tools, but it does not explicitly state when to use it versus alternatives, nor mention that it should be used before performing session mutations. Usage is inferred from the name and description rather than directly stated.

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

All SRIFT tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?