Skip to main content
Glama

SRIFT

by app.srift
OverviewAdmin

Start SRIFT Session

srift_start_session

Create a new SRIFT secure session. Returns the 7-character session ID and a shareable URL. The host approves all future joins. E2EE keys derive locally from the session ID + optional roomSecret.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomSecretNoOptional shared secret for extra-strong E2EE key derivation. Never sent to server.
sessionNameNoHuman-readable session name (optional, e.g. "Project Collab")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoDirect browser join URL to share with peers
roleNoUser role in session (host)
sessionIdYes7-character unique session room code

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / sessionName / description
      Previous value: -"Human-readable session name (optional)"New value: +"Human-readable session name (optional, e.g. \"Project Collab\")"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "role": {
+      "description": "User role in session (host)",
+      "type": "string"
+    },
+    "sessionId": {
+      "description": "7-character unique session room code",
+      "type": "string"
+    },
+    "url": {
+      "description": "Direct browser join URL to share with peers",
+      "type": "string"
+    }
+  },
+  "required": [
+    "sessionId"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses meaningful security and access-control behavior: the host approves all future joins, and E2EE keys derive locally from the session ID plus optional roomSecret. This gives an agent important context about the trust model without contradicting any annotation.

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?

The description is three tight sentences with no filler. The primary action and return values are front-loaded, followed by the most important behavioral and security details. Every sentence earns its place.

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 tool with zero required parameters, an output schema, and non-destructive mutation annotations, the description covers what the tool returns, how joins are governed, and how E2EE keys are derived. No critical operational aspect appears missing.

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 the schema already documents both roomSecret and sessionName. The description reinforces roomSecret's role in key derivation, which adds a small connection, but it does not meaningfully expand on the schema's parameter descriptions.

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 ('Create a new SRIFT secure session') and clearly distinguishes this tool from siblings like srift_join_session and srift_close_session by framing it as session creation. It also states the key outputs (7-character session ID and shareable URL), 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 Guidelines4/5

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

The description clearly implies this is the tool to use when starting a new session rather than joining or managing an existing one, and the sibling names reinforce that. It does not explicitly name alternatives or state 'use this when creating a new session,' so it stops short of full explicit routing.

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
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