Skip to main content
Glama
Dedcode14

DedcodeMCP File Manager

by Dedcode14

listar_archivos

Lists all files in the sandbox directory for the DedcodeMCP File Manager, enabling users to view and manage their stored documents.

Instructions

Lista todos los archivos en el sandbox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.ts:314-337 (handler)
    Handler for 'listar_archivos' tool: reads directory recursively from DESKTOP_DIR, lists files or reports empty.
    case "listar_archivos": {
        const archivos = await fs.readdir(DESKTOP_DIR, { recursive: true });
    
        if (archivos.length === 0) {
            return {
                content: [
                    {
                        type: "text",
                        text: "No hay archivos en el escritorio",
                    },
                ],
            };
        }
    
        const lista = archivos.join("\n- ");
        return {
            content: [
                {
                    type: "text",
                    text: `Archivos en el escritorio:\n- ${lista}`,
                },
            ],
        };
    }
  • main.ts:152-159 (registration)
    Tool registration in ListTools handler, including name, description, and empty input schema.
    {
        name: "listar_archivos",
        description: "Lista todos los archivos en el sandbox",
        inputSchema: {
            type: "object",
            properties: {},
        },
    },
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 states it lists files but doesn't describe return format (e.g., list of names, metadata), pagination, error handling, or any constraints like rate limits or permissions needed. This leaves significant gaps for an agent to use it effectively.

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 no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 no annotations, no output schema, and a simple zero-parameter tool, the description is minimal. It states what the tool does but lacks details on behavior, output format, or usage context, making it incomplete for reliable agent operation despite the low complexity.

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 0 parameters with 100% schema description coverage, so the schema already fully documents the inputs. The description doesn't need to add parameter details, and it correctly implies no inputs are required. A baseline of 4 is appropriate for a zero-parameter tool.

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 ('Lista') and resource ('archivos en el sandbox'), making the purpose understandable. However, it doesn't differentiate from potential siblings like 'leer_archivo' (which might read file contents), so it's not fully specific about scope.

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 like 'leer_archivo' or 'crear_archivo'. It lacks context about prerequisites, such as whether the sandbox must exist or be accessible, or any limitations on usage.

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