Skip to main content
Glama
ghiloufibg

Maven Project Generator MCP

by ghiloufibg

list_files

Lists all files in the current Maven project to review structure and contents for project management and organization.

Instructions

Lister tous les fichiers du projet en cours

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The listFiles function which implements the logic for listing files in the current project.
    async function listFiles() {
      if (Object.keys(currentProject.files).length === 0) {
        return {
          content: [
            {
              type: "text",
              text: "Aucun projet en cours. Creez d'abord un projet avec 'create_maven_project'.",
            },
          ],
        };
      }
    
      const filesList = Object.keys(currentProject.files)
        .sort()
        .map(file => `- ${file}`)
        .join('\n');
    
      return {
        content: [
          {
  • src/index.ts:192-198 (registration)
    The MCP tool registration for list_files.
      name: "list_files",
      description: "Lister tous les fichiers du projet en cours",
      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 what 'list' entails—whether it returns metadata, paths, or full contents; if it's paginated; or if it requires specific permissions. This leaves significant gaps for a tool that likely interacts with a project system.

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 in French that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it highly concise and well-structured for its simplicity.

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 simplicity (0 parameters, no output schema), the description is minimal but adequate for basic understanding. However, it lacks context on behavior (e.g., output format, error handling) and doesn't leverage the absence of annotations to clarify operational details, making it incomplete for informed use.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here, but doesn't compensate for any gaps since there are none. A baseline of 4 is applied for zero-parameter tools.

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 ('Lister tous les fichiers' - List all files) and the target resource ('du projet en cours' - of the current project). It uses a specific verb and identifies the resource scope, though it doesn't explicitly differentiate from sibling tools like 'generate_zip' or 'clear_project' which have different purposes.

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 (e.g., needing an active project), exclusions, or comparisons to sibling tools like 'add_any_file' for adding files or 'clear_project' for removing them.

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/ghiloufibg/maven-mcp-server'

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