Skip to main content
Glama
ghiloufibg

Maven Project Generator MCP

by ghiloufibg
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

clear_project

Remove all generated files and reset the current Maven project to its initial state, allowing for a clean restart of project generation.

Instructions

Vider le projet en cours

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:474-488 (handler)
    The actual implementation of the clear_project logic which resets the currentProject object and returns a success message.
    async function clearProject() {
  currentProject = {
    groupId: "",
    artifactId: "",
    version: "1.0.0",
    files: {},
  };

  return {
    content: [
      {
        type: "text",
        text: "Projet vide avec succes! Vous pouvez maintenant creer un nouveau projet.",
      },
    ],
  • src/index.ts:184-190 (registration)
    Registration of the clear_project tool definition for the MCP server.
      name: "clear_project",
  description: "Vider le projet en cours",
  inputSchema: {
    type: "object",
    properties: {},
  },
},

Tool Definition Quality

C2.9/5.0
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. 'Vider' suggests a destructive action, but it doesn't disclose if this deletes files permanently, requires confirmation, affects only specific project parts, or has side effects. This is inadequate for a likely mutation tool with zero annotation coverage.

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, with no wasted words. It's front-loaded and appropriately sized for a simple tool, 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 likely destructive action, the description is incomplete. It doesn't explain what 'clear' entails, what happens to the project, or what the user should expect afterward. For a tool with potential complexity and no structured support, this leaves significant gaps.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info, which is fine here. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Vider le projet en cours' (French for 'Clear the current project') states a verb ('vider' = clear) and resource ('projet en cours' = current project), giving a basic purpose. However, it's vague about what 'clear' means—does it delete files, reset configurations, or something else? It doesn't distinguish from siblings like 'list_files' or 'create_maven_project', which is a gap.

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. For example, it doesn't specify if this should be used before creating a new project with 'create_maven_project' or after listing files with 'list_files'. The description implies a context ('current project') but offers no explicit when/when-not rules or prerequisites.

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