Skip to main content
Glama
Sign In
java-jdtls-mcp-server

java-jdtls-mcp-server

by SachieWang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

java_start

Start the Java Language Server to enable code intelligence. Required before using other commands; restarts if already running.

Instructions

Start the Java Language Server (JDT.LS). Required before other commands. If already running, it will restart.

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": {
      "jdtlsHome": "<jdtlsHome>"
    },
    "name": "java_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
jdtlsHomeYesPath to JDT.LS installation root directory
workspacePathNoPath to the workspace root (default: current directory)
javaHomeNoPath to Java Home (overrides JAVA_HOME env var)
javaRuntimesNoList of Java Runtimes for different versions
mavenConfigNoCustom Maven configuration

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Discloses that it starts the server and restarts if already running, but no annotations are provided to cover safety/permissions; lacks detail on failure modes or environment requirements.

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?

Two sentences, front-loads the action and key behavior, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Misses return value description or outcome indication; given there is no output schema, description should hint at what happens after call.

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?

Schema coverage is 100% so baseline is 3; description does not add any additional parameter context beyond what schema already provides.

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

Purpose5/5

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

The description clearly states the tool starts the Java Language Server, distinguishes it from other commands by noting it is required first, and mentions restart behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States 'Required before other commands', which provides context, but does not differentiate from sibling 'java_restart' which also restarts, leaving ambiguity.

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

Deploy Server

Other Tools