SRIFT

Diagnose Network Transports

srift_net_diagnose

Read-only

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.6/5.0

Behavior5/5

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

Annotations declare read-only and non-destructive. The description reinforces this: 'Read-only apart from that temporary self-test link,' and explains the temporary self-test link creation when deep=true. This adds behavioral context beyond annotations, including the output format (WORKS/WARN/BLOCKED) and the plan.

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 description is informative but relatively long, covering many checks and behaviors. However, each sentence contributes value, and the key points are front-loaded. A 4 reflects its efficiency for the complexity.

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?

Given the tool's complexity (many check categories, output schema exists, and deep flag behavior), the description covers the purpose, output, usage, and the temporary link exception. It is complete for an agent to understand when and how to call 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 covers both parameters with detailed descriptions. The tool description adds minimal extra semantic value, only restating deep's effect. With high schema coverage, baseline 3 is appropriate.

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' with a clear resource 'SRIFT on this machine' and enumerates the categories of checks. Clearly distinguishes from sibling session/transfer tools.

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

Usage Guidelines5/5

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

Explicitly provides when to run: 'Run this first when a transfer stalls or a quick-share call fails for an unclear reason.' This gives clear usage context and positions it as the diagnostic first step.

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.