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

java-jdtls-mcp-server

by SachieWang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

java_get_file_symbols

Retrieve all symbols defined in a Java file, including classes, methods, and fields. Provide the absolute file path or URI to get the complete symbol listing.

Instructions

Get all symbols (classes, methods, fields) defined in a specific file.

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>"
    },
    "name": "java_get_file_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYesAbsolute path to the Java file or a URI (e.g. jdt://...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Without annotations, the description only states it retrieves symbols. It does not disclose performance implications, whether results are complete, or if it requires file system access. Minimal disclosure for a read operation.

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?

Single sentence, no filler, highly efficient for the content it conveys.

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?

The description is minimal and lacks details about return format, nested symbols, or how it differs from java_open_file. It does not provide enough context for an agent to decide between similar tools.

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% (one parameter fully described). The description adds no extra meaning beyond the parameter's own description, so baseline 3 applies.

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 gets symbols (classes, methods, fields) from a specific file, distinguishing it from sibling tools like java_search_symbols which search across the workspace.

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 on when to use this tool versus alternatives like java_search_symbols or java_get_definition. The description implies file-specific use but doesn't set boundaries.

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