Skip to main content
Glama
fredriksknese

mcp-openmediavault

get_ftp_settings

Retrieve global FTP service configuration details such as port number, maximum connection limits, and activation status for network file transfers.

Instructions

Get global FTP service settings including port, max connections, and enabled status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'get_ftp_settings' tool using server.tool(). Includes the tool name, description, empty input schema ({}), and the async handler function that calls client.rpc('FTP', 'getSettings', {}) to fetch FTP service settings.
    server.tool(
      "get_ftp_settings",
      "Get global FTP service settings including port, max connections, and enabled status",
      {},
      async () => {
        try {
          const result = await client.rpc("FTP", "getSettings", {});
          return toolResult(JSON.stringify(result, null, 2));
        } catch (error) {
          return toolResult(`Error fetching FTP settings: ${error}`, true);
        }
      },
    );
  • Helper function 'toolResult' that formats the tool response with content array and optional error flag. Used by the get_ftp_settings handler to format its output.
    function toolResult(text: string, isError = false) {
      return { content: [{ type: "text" as const, text }], isError };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), but doesn't mention permissions required, whether it's safe to call frequently, response format, or potential errors. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 a single, efficient sentence that front-loads the core purpose ('Get global FTP service settings') and provides specific examples without redundancy. Every word earns its place, and there's no wasted verbiage or structural issues.

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?

Given the tool's simplicity (zero parameters, no output schema, no annotations), the description is adequate but minimal. It covers the what (FTP settings) and examples of settings, but lacks behavioral context like permissions or response format. For a read-only tool with no complex inputs/outputs, this is the minimum viable description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters (schema coverage 100%), so no parameter documentation is needed. The description appropriately doesn't discuss parameters, and the baseline for zero-parameter tools is 4. It adds value by specifying what settings are retrieved (port, max connections, enabled status) without unnecessary detail.

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 clearly states the verb 'Get' and the resource 'global FTP service settings', with specific examples (port, max connections, enabled status). It distinguishes from siblings like 'list_ftp_shares' by focusing on service configuration rather than share listings. However, it doesn't explicitly differentiate from other 'get_*_settings' tools (e.g., get_nfs_settings, get_smb_settings) beyond the FTP specificity.

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. It doesn't mention prerequisites, timing considerations, or comparisons with similar tools like 'get_ssh_settings' or 'list_ftp_shares'. The agent must infer usage from the name and description alone without explicit context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fredriksknese/mcp-openmediavault'

If you have feedback or need assistance with the MCP directory API, please join our Discord server