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

java-jdtls-mcp-server

by SachieWang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

java_get_hover

Retrieve hover information for a Java symbol by providing its file path, line number, and character offset.

Instructions

Get hover information for a symbol.

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": {
      "filePath": "<filePath>",
      "line": "<line>",
      "character": "<character>"
    },
    "name": "java_get_hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYesAbsolute path to the file or a URI (e.g. jdt://...)
lineYesLine number (0-indexed)
characterYesCharacter offset (0-indexed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, prerequisites, or limitations. It only states the action without additional context.

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 sentence that is concise and front-loaded. Every word is necessary and there is no redundant information.

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?

There is no output schema, and the description does not explain what the hover information contains or any return structure. For a tool with three parameters and no output schema, the description should provide more context.

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 description coverage is 100% as all three parameters have descriptions. The tool description itself does not add further meaning beyond the schema, meeting the baseline of 3.

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 uses a specific verb 'Get' and resource 'hover information' for a 'symbol'. It clearly distinguishes from sibling tools like java_get_definition or java_get_references, which serve 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 Guidelines3/5

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

The description implies usage when hover information is needed, but it does not provide explicit guidance on when to use this tool versus alternatives like java_get_definition or java_get_references.

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