Skip to main content
Glama
Sign In
sftp-mcp

sftp-mcp

by Guipegoraro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sftp_info

Read-only

Retrieve file or folder metadata, including type, size, dates, and permissions, from an SFTP server to verify details before reading or downloading.

Instructions

Tipo, tamanho, datas e permissoes de um arquivo ou pasta do servidor.

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
perfilYes
caminhoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 state readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered without the description. The description adds useful content about what metadata is returned, but says nothing about behavior on missing paths, required connectivity/profile, or permissions needed to read metadata.

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?

A single compact sentence with the returned fields front-loaded and no filler. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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?

For a simple read-only lookup with no output schema, the description usefully enumerates the returned attributes, but it leaves gaps on parameter meaning (especially 'perfil') and on error/missing-path behavior. Adequate but not complete.

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% and the schema only supplies bare titles 'Perfil' and 'Caminho'. The description implies that 'caminho' is a server-side file or folder path, but adds no meaning at all for 'perfil' (presumably a connection profile), leaving one of two required 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 names the resource (a file or folder on the server) and enumerates the returned attributes (type, size, dates, permissions), which makes it distinguishable from listing siblings like sftp_listar. The verb is only implied by the tool name; the sentence itself is a noun phrase rather than an explicit action statement.

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 guidance on when to use this tool versus sftp_listar, sftp_buscar or sftp_ler. The phrase 'de um arquivo ou pasta' hints at a single-item scope, but no prerequisites or exclusions are stated.

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