SRIFT

Diagnose Network Transports

srift_net_diagnose

Read-onlyIdempotent

Diagnose SRIFT on this machine: connectivity (DNS, proxy, HTTPS/TLS, WebSocket relay, UDP/P2P, peer discovery, clock), the local runtime (loopback, background processes, daemon + version, disk) and the environment (sandbox/CI/container detection, curl). Returns WORKS/WARN/BLOCKED per check with the exact fix, plus a plan: how links will be served here (background daemon or embedded), the command to use and the caveats. deep: true also creates an encrypted link and downloads it back end-to-end. Read-only apart from that temporary self-test link. Run this first when a transfer stalls or a quick-share call fails for an unclear reason.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`deep`	No	Also run an end-to-end self-test: create an encrypted single-use link and download it back through the relay (≈2 MB, a few seconds).
`fresh`	No	Force a fresh probe instead of returning a cached result (slower, more accurate).

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	True if the diagnostic ran successfully (independent of what it found)
`env`	No	Relevant environment (proxy vars, sandbox indicators, Node version, etc.)
`base`	No	The SRIFT server that was probed
`plan`	No	serveFrom (background-daemon \| embedded \| unavailable), transport, shareCommand, downloadCommand, advice[] — what to do in this environment
`rungs`	No	Each transport rung checked, in order, with status and a fix hint if blocked
`context`	No	runtime (mcp, cli, npx, binary, pypi…), cliVersion, serverVersion, daemonVersion
`summary`	No	One-line conclusion
`verdict`	No	"ok", "degraded", or "blocked"
`selfTest`	No	deep only: { ok, ms, bytes, mbps, via, error? }
`checkedAt`	No	When the probe ran (ISO 8601); cached results show an older time
`recommendedMode`	No	"relay" when links can be served from here, otherwise "none"

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

addedOutput schema / properties / base

Added value: +{
+  "description": "The SRIFT server that was probed",
+  "type": "string"
+}

addedOutput schema / properties / checkedAt

Added value: +{
+  "description": "When the probe ran (ISO 8601); cached results show an older time",
+  "type": "string"
+}

AddedSep 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/destructive/idempotent, and the description goes beyond them by disclosing the one side effect (deep:true creates a temporary encrypted self-test link) and the caching behavior of fresh. It stops short of stating permissions or failure semantics, but the added context is real.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, and the operational trigger closes the paragraph where an agent scans last. It is dense and runs long as a single sentence-heavy block, but nearly every clause adds a distinct check category or behavior.

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?

An output schema exists and the description still previews the return shape (WORKS/WARN/BLOCKED per check plus a plan with command and caveats). Combined with full parameter coverage and the side-effect disclosure, an agent has everything needed to call and interpret it.

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 description coverage is 100%, so both booleans are already fully documented, including the ~2 MB / few seconds detail. The description restates deep's behavior without adding syntax or constraints beyond the schema, so 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 (Diagnose) and scope (SRIFT on this machine) and enumerates exactly what is checked across connectivity, runtime, and environment layers. This clearly separates it from the sibling session-management tools, so an agent can pick it without opening the schema.

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?

Gives an explicit trigger: 'Run this first when a transfer stalls or a quick-share call fails for an unclear reason,' which tells the agent precisely when to reach for it. It does not name a when-not condition or alternative tool, but no closely competing diagnostic sibling exists.

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

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.