Java Project Runner MCP

project_register

Register a Maven project by adding its pom.xml path and settings to the Java Project Runner configuration for build and run management.

Instructions

Add a project to ~/.java-project-runner/projects.json (path must contain pom.xml)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "name": "<name>",
      "path": "<path>",
      "jarPath": "<jarPath>",
      "enabled": "<enabled>"
    },
    "name": "project_register"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`path`	Yes
`enabled`	Yes
`jarPath`	Yes
`jvmArgs`	No
`javaHome`	No
`profiles`	No
`buildGoal`	No
`skipTests`	No
`defaultProfile`	No
`healthCheckUrl`	No
`stopTimeoutSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1Nov 2, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the concrete side effect (persisting to the projects.json registry file), which is the most important behavior for a mutation tool. However, duplicate-id handling, failure modes, and whether the entry is created or overwritten are undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the effect front-loaded and no filler. Its brevity is economical rather than padded, though the parenthetical constraint is cryptic out of context.

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?

A 13-parameter mutation tool with no annotations, no output schema, and 0% schema coverage is served by one sentence that explains only the destination file and one path rule. An agent cannot correctly populate the required jarPath or decide whether registration overwrites an existing id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 0% schema description coverage, the description must compensate for 13 parameters and it only constrains one ('path must contain pom.xml'), which is genuinely useful beyond the bare minLength. The other twelve (id vs. name, jarPath, enabled, jvmArgs, javaHome, profiles, buildGoal, skipTests, defaultProfile, healthCheckUrl, stopTimeoutSeconds) are entirely undocumented anywhere.

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?

States a specific verb and resource ('Add a project') plus the concrete effect (writes to ~/.java-project-runner/projects.json), which separates it from project_unregister and other siblings. It does not clarify how it differs from project_update, so it falls short of 5.

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 parenthetical 'path must contain pom.xml' is a validation constraint, not usage guidance. Nothing says when to register vs. update, what happens if the project already exists, or that this should be called before build/start.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server