Skip to main content
Glama

FTP-Zugänge anzeigen

get_ftp_accounts
Read-only

FTP-Zugänge einer Domain auflisten (live von Plesk): den Hauptzugang des Abonnements (der Login aus der Willkommens-Mail — sein Passwort kann der Chat nicht zurücksetzen, es ist zugleich das SSH-Passwort und wird in Plesk geändert) und die zusätzlich angelegten Zugänge mit Startverzeichnis. Letztere liefern den Login, den reset_ftp_password braucht — Kunden kennen ihren FTP-Benutzernamen meist nicht auswendig. Dass es keine ZUSÄTZLICHEN Zugänge gibt, ist ein normaler Zustand, kein Fehler; ganz ohne FTP-Zugang ist eine Domain mit Abonnement nie.

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": {
      "domain": "<domain>"
    },
    "name": "get_ftp_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDie Domain, z. B. example.de

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description goes beyond that: it says the data is live from Plesk, notes that the main account's password cannot be reset by the chat and is also the SSH password, and clarifies that an empty additional-accounts list is not an error. This is meaningful operational context not present in structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action, but it is fairly long for a single-parameter read tool and packs three distinct ideas (account types, password reset caveat, expected-empty state) into one dense paragraph. It is informative but not optimally tight.

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

Completeness4/5

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

For a simple read with one fully documented parameter and read-only annotations, the description covers the important behavioral nuances: what is returned, what can't be done with it, and what constitutes a normal result. Without an output schema, it sufficiently signals the shape of the return data (main account + additional accounts with start directory).

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 coverage is 100% and the single 'domain' parameter is fully documented in the schema. The description implies the domain scoping but adds no format, syntax, or semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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?

Specific verb (auflisten) + resource (FTP-Zugänge einer Domain) with a clear scope split: the subscription's main account versus additionally created accounts with start directory. It is distinguishable from siblings like get_email_accounts or get_databases.

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

Usage Guidelines4/5

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

It explicitly names reset_ftp_password as the downstream consumer and explains why the list is needed (customers don't remember their FTP usernames). It also sets an expectation that 'no additional accounts' is a normal state, which prevents wasted follow-up. No explicit when-not-to-use is given, but the routing to a sibling is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources