Skip to main content
Glama

Configure Headless JavaFX

fix_javafx_headless
Idempotent

Detect and explain headless JavaFX problems, then generate the configuration needed to fix them. Run a dry run by default or apply the change.

Instructions

Detect and explain headless JavaFX problems and generate the required configuration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fix_javafx_headless"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNoWrite the change; default false performs a dry run
mainClassNoOptional main class name to target
projectPathNoPath to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is partly covered. The description adds that it both diagnoses and generates configuration, but it does not say which files get written, whether existing files are overwritten, or that the default is a dry run, which is left entirely to the schema.

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?

One compact sentence with no filler, front-loading the diagnostic action before the remediation. It is efficient, though very terse for a tool that both reports and mutates project configuration.

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?

For a three-parameter tool with no output schema that can write configuration, the description leaves open what the explanation output looks like and what exactly is generated or modified. The structured fields cover the safety hints and parameters, but an agent still lacks behavioral detail about the write step.

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%, so the schema already documents apply, mainClass and projectPath, including the dry-run default. The description adds no extra meaning about these parameters, so the baseline of 3 applies.

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?

The description names concrete verbs (detect, explain, generate) and a specific resource (headless JavaFX configuration), so an agent can distinguish it from siblings such as fix_all or fix_maven_dependencies. It stops short of explicitly naming which sibling to use instead, but the domain is unambiguous.

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?

Usage is only implied: an agent can infer the tool applies when a headless JavaFX error occurs, but the description never states when to prefer it over fix_all or when a problem is out of scope. There is no explicit when-not guidance.

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