Skip to main content
Glama
fkom13

MCP SFTP Orchestrator

by fkom13

Supprimer un alias de serveur

server_remove

Remove a server alias from the MCP SFTP Orchestrator configuration to manage remote server connections.

Instructions

Supprime un alias de serveur de la configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aliasYesNom de l'alias à supprimer

Implementation Reference

  • Core logic for removing a server alias from the servers.json configuration file.
    async function removeServer(alias) {
        const servers = await readServers();
        if (!servers[alias]) {
            throw new Error(`L'alias '${alias}' n'existe pas.`);
        }
        delete servers[alias];
        await writeServers(servers);
        return { success: true, message: `Serveur '${alias}' supprimé.` };
    }
  • MCP tool handler function that invokes servers.removeServer and formats the response.
    async (params) => {
        try {
            const result = await servers.removeServer(params.alias);
            return { content: [{ type: "text", text: result.message }] };
        } catch (e) {
            const errorPayload = {
                toolName: "server_remove",
                errorCode: "TOOL_EXECUTION_ERROR",
                errorMessage: e.message
            };
            return { content: [{ type: "text", text: JSON.stringify(errorPayload, null, 2) }], isError: true };
        }
    }
  • Input schema for the server_remove tool using Zod.
    {
        title: "Supprimer un alias de serveur",
        description: "Supprime un alias de serveur de la configuration.",
        inputSchema: z.object({
            alias: z.string().describe("Nom de l'alias à supprimer")
        })
    },
  • server.js:94-116 (registration)
    Registration of the server_remove tool on the MCP server.
    server.registerTool(
        "server_remove",
        {
            title: "Supprimer un alias de serveur",
            description: "Supprime un alias de serveur de la configuration.",
            inputSchema: z.object({
                alias: z.string().describe("Nom de l'alias à supprimer")
            })
        },
        async (params) => {
            try {
                const result = await servers.removeServer(params.alias);
                return { content: [{ type: "text", text: result.message }] };
            } catch (e) {
                const errorPayload = {
                    toolName: "server_remove",
                    errorCode: "TOOL_EXECUTION_ERROR",
                    errorMessage: e.message
                };
                return { content: [{ type: "text", text: JSON.stringify(errorPayload, null, 2) }], isError: true };
            }
        }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a destructive action ('Supprime'), but lacks details on permissions needed, reversibility, error handling, or system impact. This is a significant gap for a mutation tool.

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 with zero waste, clearly front-loading the core action. It's appropriately sized for a simple tool with one parameter.

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

Completeness2/5

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

Given the tool's destructive nature, no annotations, and no output schema, the description is incomplete. It fails to address critical aspects like confirmation prompts, return values, or error scenarios, leaving gaps for safe agent operation.

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 100%, so the parameter 'alias' is well-documented in the schema. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, resulting in a baseline score of 3.

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 ('Supprime') and resource ('un alias de serveur de la configuration'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'server_add' or 'api_remove', which would require a 5.

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 guidance is provided on when to use this tool versus alternatives like 'server_add' or 'api_remove', nor are prerequisites or exclusions mentioned. The description only states what it does, not when to apply it.

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/fkom13/mcp-sftp-orchestrator'

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