sftp-mcp

Overview Schema Source Related Servers Discussions Admin

sftp_buscar

Read-only

Search files and folders on an SFTP server by case-insensitive glob pattern from a starting path, with a configurable depth limit and no folder-link traversal.

Instructions

Busca por nome (glob, sem diferenciar maiusculas) a partir de uma pasta, descendo ate a profundidade maxima do perfil (padrao 5). Nao segue link de pasta.

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": {
      "perfil": "<perfil>",
      "caminho": "<caminho>"
    },
    "name": "sftp_buscar"
  }
}

Input Schema

Name	Required	Default
`tipo`	No	qualquer
`padrao`	No	*
`perfil`	Yes
`caminho`	Yes
`profundidade`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint, so the safety profile is covered; the description adds real value beyond them by disclosing recursion depth semantics (profile max, default 5) and that folder symlinks are not traversed. It still omits result limits, ordering, and error behavior on missing paths.

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?

Two compact clauses with no filler, and the key search semantics are front-loaded. Slightly dense phrasing without parameter naming makes it a bit harder to map onto the five inputs.

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?

A reasonably complex 5-parameter tool with 0% schema coverage and no output schema; the description covers recursion and link behavior but leaves three parameters and the return shape undocumented. Adequate but with clear gaps an agent would hit on first call.

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 description must compensate, yet it only clarifies padrao (glob, case-insensitive) and profundidade (default capped by profile). The required perfil and caminho params, plus the tipo enum (qualquer/arquivo/pasta), are left entirely 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?

States a specific verb and resource: glob-based name search starting from a folder, distinguishing it from sftp_listar (listing) - though it does not name that sibling explicitly. The scope (max depth from profile, no folder-link following) sharpens the purpose further.

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?

No explicit when-to-use or when-not-to-use guidance and no named alternative among the 11 siblings (sftp_listar, sftp_info). The mention of depth and non-following links is behavioral, not a routing rule for choosing this tool over listing.

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

Deploy Server