Skip to main content
Glama
Sign In
unfour

unfour

by zyqzyq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

List SSH Directory

unfour.ssh.list_dir
Read-onlyIdempotent

Lists a bounded remote directory over SSH and returns structured entry summaries when remote find is available, so you can inspect saved connections safely in dev, test, or production.

Instructions

Lists a bounded remote directory through SSH and returns structured entry summaries when the remote find utility is available. Safe in dev/test/prod.

Input Schema

NameRequiredDescriptionDefault
pathYes
limitNo
timeoutMsNo
workspaceIdNo
connectionIdYes

Output Schema

NameRequiredDescriptionDefault
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedOutput schema / properties
      Added value: +{
+  "warnings": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}
  2. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is largely covered. The description adds useful behavioral context by noting that results are 'bounded' and that structured summaries depend on the remote find utility being available, though it does not explain fallback behavior or permission requirements.

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 two concise sentences with the main action front-loaded. It avoids repetition and does not waste space on boilerplate.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter tool with 0% schema description coverage, the description is too thin. While annotations and the output schema reduce the need to explain safety and return values, the description still leaves key parameters and when-to-use alternatives unexplained.

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%, so the schema itself provides no meaning for the five parameters. The description hints that 'bounded' relates to limit and 'remote directory' relates to path, but it says nothing about connectionId, timeoutMs, or workspaceId, leaving most parameters unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Lists a bounded remote directory through SSH.' It is clearly distinct from SSH siblings like read_file, write_file, and exec, but it does not explicitly name alternatives or clarify the boundary with those tools.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as read_file, exec, or list_connections. 'Safe in dev/test/prod' is an environment safety note, not a usage guideline, and there are no explicit exclusions or prerequisites.

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

Deploy Server

Other Tools