Skip to main content
Glama
Dedcode14

DedcodeMCP File Manager

by Dedcode14

eliminar_archivo

Delete files from your system using the DedcodeMCP File Manager. Specify the filename to remove unwanted files and manage storage.

Instructions

Elimina un archivo del sistema

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nombreYesNombre del archivo a eliminar

Implementation Reference

  • main.ts:286-312 (handler)
    Handler for the 'eliminar_archivo' tool. Parses input using EliminarArchivoSchema, constructs file path on desktop, validates path access, deletes the file using fs.unlink, and returns a success message or error if path invalid.
    case "eliminar_archivo": {
        const { nombre } = EliminarArchivoSchema.parse(args);
        const ruta = path.join(DESKTOP_DIR, nombre);
    
        if (!validarRuta(ruta)) {
            return {
                content: [
                    {
                        type: "text",
                        text: "Error: Solo se permite acceso al escritorio",
                    },
                ],
                isError: true,
            };
        }
    
        await fs.unlink(ruta);
    
        return {
            content: [
                {
                    type: "text",
                    text: `Archivo eliminado: ${nombre}`,
                },
            ],
        };
    }
  • main.ts:62-64 (schema)
    Zod schema defining the input for 'eliminar_archivo' tool: requires 'nombre' string parameter.
    const EliminarArchivoSchema = z.object({
        nombre: z.string().describe("Nombre del archivo a eliminar"),
    });
  • main.ts:138-151 (registration)
    Tool registration in ListToolsRequestHandler response, specifying name, description, and inputSchema matching the Zod schema.
    {
        name: "eliminar_archivo",
        description: "Elimina un archivo del sistema",
        inputSchema: {
            type: "object",
            properties: {
                nombre: {
                    type: "string",
                    description: "Nombre del archivo a eliminar",
                },
            },
            required: ["nombre"],
        },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Elimina' clearly indicates a destructive operation, but the description doesn't disclose whether deletion is permanent or reversible, what permissions are required, whether there are confirmation prompts, or what happens on success/failure. For a destructive tool with zero annotation coverage, this is a significant gap.

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 wasted words. It's appropriately sized for a simple delete operation and gets straight to the point without unnecessary elaboration.

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?

For a destructive file deletion tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion (success message, error handling), whether deletion is permanent, what permissions are needed, or how it differs from moving files. Given the complexity and risk of file deletion, more context is needed.

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 schema already documents the single parameter 'nombre' (name of file to delete). The description doesn't add any additional parameter semantics beyond what the schema provides, such as path requirements, file format restrictions, or wildcard support. Baseline 3 is appropriate when schema does the documentation.

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 action ('Elimina' - deletes) and resource ('un archivo del sistema' - a file from the system), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'mover_archivo' (move file) or 'editar_archivo' (edit file) beyond the basic verb distinction.

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 about when to use this tool versus alternatives. With siblings like 'mover_archivo' (move file) and 'editar_archivo' (edit file), there's no indication of when deletion is appropriate versus moving or editing, nor any prerequisites or constraints mentioned.

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/Dedcode14/DedcodeMCP'

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