Skip to main content
Glama
Dedcode14

DedcodeMCP File Manager

by Dedcode14

mover_archivo

Move or rename files by specifying source and destination paths to organize your file system.

Instructions

Mueve o renombra un archivo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
origenYesRuta/nombre del archivo origen
destinoYesRuta/nombre del archivo destino

Implementation Reference

  • main.ts:256-284 (handler)
    The switch case handler for 'mover_archivo' that parses arguments using the schema, validates paths restricted to desktop, creates destination directory if needed, renames the file using fs.rename, and returns success or error message.
    case "mover_archivo": {
        const { origen, destino } = MoverArchivoSchema.parse(args);
        const rutaOrigen = path.join(DESKTOP_DIR, origen);
        const rutaDestino = path.join(DESKTOP_DIR, destino);
    
        if (!validarRuta(rutaOrigen) || !validarRuta(rutaDestino)) {
            return {
                content: [
                    {
                        type: "text",
                        text: "Error: Solo se permite acceso al escritorio",
                    },
                ],
                isError: true,
            };
        }
    
        await fs.mkdir(path.dirname(rutaDestino), { recursive: true });
        await fs.rename(rutaOrigen, rutaDestino);
    
        return {
            content: [
                {
                    type: "text",
                    text: `Archivo movido o renombrado: ${origen} a ${destino}`,
                },
            ],
        };
    }
  • main.ts:57-60 (schema)
    Zod schema defining input parameters 'origen' and 'destino' for the mover_archivo tool.
    const MoverArchivoSchema = z.object({
        origen: z.string().describe("Ruta/nombre del archivo origen"),
        destino: z.string().describe("Ruta/nombre del archivo destino"),
    });
  • main.ts:120-137 (registration)
    Tool registration in the ListTools response, including name, description, and inputSchema matching the Zod schema.
    {
        name: "mover_archivo",
        description: "Mueve o renombra un archivo",
        inputSchema: {
            type: "object",
            properties: {
                origen: {
                    type: "string",
                    description: "Ruta/nombre del archivo origen",
                },
                destino: {
                    type: "string",
                    description: "Ruta/nombre del archivo destino",
                },
            },
            required: ["origen", "destino"],
        },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It states the action ('Mueve o renombra') but doesn't disclose critical traits like whether it overwrites existing files, requires specific permissions, handles errors, or affects file metadata. This is inadequate 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 perfectly concise - a single Spanish phrase that directly states the tool's function with zero wasted words. It's front-loaded and efficiently communicates the core purpose.

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 file mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens on success/failure, whether renaming is just moving within same directory, or how it interacts with sibling tools. The context demands more completeness for safe agent use.

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?

The description adds no parameter semantics beyond what the schema already provides (100% coverage). The schema descriptions clearly explain 'origen' as source path/name and 'destino' as destination path/name. The baseline score of 3 reflects adequate schema documentation without description enhancement.

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 tool's purpose with specific verbs ('Mueve o renombra') and resource ('un archivo'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'editar_archivo' or 'crear_archivo', which prevents a perfect score.

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. There's no mention of prerequisites, when not to use it, or how it differs from siblings like 'editar_archivo' (which might modify content) or 'crear_archivo' (which creates new files).

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