Skip to main content
Glama

Check Maven Dependencies

fix_maven_dependencies
Read-onlyIdempotent

Detect incorrect or missing Maven dependencies and suggest fixes for a project, with a check or fix action that never applies changes automatically.

Instructions

Detect and report incorrect or missing Maven dependencies with suggested fixes.

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_maven_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNocheck (default) or fix; fixes are suggested, never applied
projectPathNoPath to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and "suggested fixes" is consistent with a non-mutating tool. The description adds nothing further, however: it does not say what is inspected, whether a Maven/IDE environment is required, or how results are surfaced.

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?

A single tight sentence with the core purpose front-loaded and no filler. It is arguably under-specified rather than bloated, which is a completeness problem rather than a structural one.

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?

With no output schema, the description is the only place to learn what a caller gets back (a report? a file list?), and it does not say. For a two-parameter, read-only check tool with full schema coverage the definition is adequate but leaves real gaps.

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% — both action (check vs fix) and projectPath are documented in the schema, including the key note that fixes are suggested but never applied. The description adds no parameter meaning beyond that, so the baseline 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?

"Detect and report incorrect or missing Maven dependencies with suggested fixes" gives a specific verb (detect/report) and resource (Maven dependencies). It stops short of distinguishing itself from adjacent tools such as fix_all or analyze_code, which an agent could plausibly pick instead.

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?

The description offers no when-to-use guidance, no prerequisites (e.g. requires a Maven project), and no routing to or away from alternatives. The only mode guidance lives in the schema's action parameter, not in the description.

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