unfour

Overview Schema Source Related Servers Discussions Admin

Run SSH Diagnostic Command

unfour.ssh.run_diagnostic

Read-onlyIdempotent

Runs a single read-only diagnostic command on a saved SSH connection through the Unfour command bus and returns captured stdout/stderr for allowlisted checks.

Instructions

Runs a single read-only diagnostic command on a saved SSH connection through the Unfour command bus and returns captured stdout/stderr. Safe in dev/test/prod for allowlisted diagnostics. For broader command execution use unfour.ssh.exec, which applies environment policy and high-risk confirmation.

Input Schema

Name	Required	Description	Default
`command`	Yes
`timeoutMs`	No
`workspaceId`	No
`connectionId`	Yes

Output Schema

Name	Required	Description	Default
`warnings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.12.0Oct 24, 2026

addedOutput schema / properties

Added value: +{
+  "warnings": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}

First observedv0.1.0Aug 20, 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, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real context beyond them: the call is gated to allowlisted diagnostics and routed through the command bus, and it returns captured stdout/stderr. It stops short of describing timeout behavior, error surfaces, or what happens to non-allowlisted commands.

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?

Two tight sentences with no filler. The capability statement leads, and the sibling routing guidance follows it, so the most decision-relevant information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 notes stdout/stderr capture, so return values need no elaboration. However, for a 4-parameter tool with zero schema descriptions, the silence on timeoutMs and workspaceId leaves an agent guessing how to scope the call or bound execution time.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 4 parameters, so the burden falls entirely on the description — and it names none of them. Only faint implication exists ('saved SSH connection' implies connectionId references a stored connection; 'single ... command' implies no script chaining). timeoutMs and workspaceId are completely unaddressed.

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 and resource ('Runs a single read-only diagnostic command on a saved SSH connection') and names the mechanism ('through the Unfour command bus'). It explicitly distinguishes itself from the sibling unfour.ssh.exec, so an agent can pick between the two without opening either schema.

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?

Gives a positive condition ('safe in dev/test/prod for allowlisted diagnostics') and a negative/alternative condition ('for broader command execution use unfour.ssh.exec, which applies environment policy and high-risk confirmation'). The routing decision is fully explicit.

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

Deploy Server