Skip to main content
Glama
Sign In
jons-mcp-java

jons-mcp-java

by jonmmease
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

symbol_info

Retrieve hover information for a Java symbol at a specified position. Provide file path, line, and character to get symbol details.

Instructions

Get hover information for a symbol at the given position.

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

Input Schema

NameRequiredDescriptionDefault
file_pathYes
lineYes
characterYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description must carry behavioral disclosure. It only implies read-only via 'Get', but lacks details on performance, side effects, or error conditions.

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?

A single, focused sentence with no extraneous content. Every word serves the purpose of explaining the tool's function.

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 the tool's simplicity and the existence of an output schema, the description is still insufficient: it provides no usage context nor parameter details. The agent would lack guidance on when to use symbol_info vs definition or references.

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

Parameters1/5

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

The input schema has 3 required parameters with 0% description coverage in the schema. The description adds no semantic meaning to the parameters; it only generically references 'the given position'. No parameter formats or examples are provided.

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 verb 'Get' and resource 'hover information' with the precise scope 'at a given position'. This distinguishes it from sibling tools like 'definition' or 'references', which return different symbol information.

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. The description only states function, not context or prerequisites.

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