Skip to main content
Glama
remote-ssh-mcp
by RuiFG

ssh_glob

Read-only

Find remote files and relative paths over SFTP using glob patterns, including **, with bounded results and no recursion into directory symlinks.

Instructions

Find relative paths through SFTP using glob patterns, including **. Does not recurse into directory symlinks. Results and traversal are bounded.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hostId": "<hostId>",
      "pattern": "<pattern>"
    },
    "name": "ssh_glob"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
limitNo
hostIdYesRequired stable host ID returned by ssh_list_hosts. Names are not accepted.
patternYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, open-world, non-idempotent, so the safety profile is covered. Beyond that, the description adds two genuinely useful behaviors: no recursion into directory symlinks, and that both results and traversal are bounded. 'Bounded' is left undefined (no mention of truncation signaling), which keeps it short of a 5.

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?

Three tight sentences with the core action front-loaded and caveats after it; no filler. The closing sentence is slightly vague ('bounded' without specifics), so it earns its place only partially.

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?

With no output schema and thin in-schema parameter documentation, the description carries more burden than it meets: it never states the return shape (list of relative paths?), how limit interacts with truncation, or the format/syntax expectations for path. It is adequate to start a call but leaves notable gaps for a 4-parameter tool.

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 only 25% — only hostId is documented in-schema, while path, pattern, and limit are bare. The description partially compensates by explaining pattern semantics (glob, including **) and implying path is the search base with relative outputs, but it says nothing about what limit does or how truncation surfaces.

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?

States a specific verb and resource: 'Find relative paths through SFTP using glob patterns.' That distinguishes it from action-oriented siblings like ssh_grep (content search) or ssh_read_file (content retrieval) without naming them. A tighter definition would have explicitly contrasted it with shell-based globbing via ssh_shell_exec.

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?

There is no when-to-use guidance and no exclusions: nothing says whether to prefer this over ssh_shell_exec or ssh_grep for locating files, nor what a caller gets when the pattern must be anchored. Usage is only implied by the verb 'Find'.

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