mcp

Add a project dependency

addDependency

Add an extra application dependency to the generated Maven or Gradle build. Bootify already adds dependencies required by selected project features. Call listAvailableDependencies to find supported coordinates, then pass the returned groupId:artifactId. Spring Boot supplies the compatible dependency version.

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": {
      "projectId": "<projectId>",
      "dependency": "<dependency>"
    },
    "name": "addDependency"
  }
}

Input Schema

Name	Required	Description	Default
`projectId`	Yes	The project ID returned by startProject
`dependency`	Yes	Maven coordinates: groupId:artifactId[:version]

Output Schema

Name	Required	Description
`changes`	Yes	Only settings whose values actually changed, including automatic effects, using final stored values in MCP format. Nested objects contain changed properties only. Empty when no settings changed; values that are no longer exposed are omitted.
`projectId`	Yes	The project ID returned by startProject
`affectedAreas`	Yes	Object lists changed directly or by automatic effects. Lists are not returned; use getProject with these details when needed. Empty for no list changes.
`userProjectChanged`	No	Present only once when the project appears to have been changed by the user since the preceding MCP call within the last two hours

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedOutput schema / properties / affectedAreas / items / enum

Previous value: -[
-  "APP_MODULES",
-  "ENUMS",
-  "DATA_OBJECTS",
-  "ENTITIES",
-  "RELATIONS",
-  "INDEXES",
-  "REST_CONTROLLERS",
-  "FRONTEND_CONTROLLERS",
-  "SECURITY_CONFIGS"
-]New value: +[
+  "APP_MODULES",
+  "ENUMS",
+  "DATA_OBJECTS",
+  "ENTITIES",
+  "RELATIONS",
+  "INDEXES",
+  "BREAKPOINTS",
+  "REST_CONTROLLERS",
+  "FRONTEND_CONTROLLERS",
+  "SECURITY_CONFIGS"
+]

First observedSep 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations mark this as a non-read-only, non-idempotent, non-destructive write. The description adds real behavior beyond that: Bootify already supplies feature-required dependencies, the version is not the caller's responsibility (Spring Boot supplies the compatible version), and coordinates must come from listAvailableDependencies. It does not address what happens on duplicate adds, which idempotentHint=false implies is a real concern.

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?

Three short sentences, front-loaded with the action and its scope, followed by workflow and version policy. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the description covers purpose, prerequisite workflow, and version handling for a 2-parameter tool. The only real gap is the duplicate-add / non-idempotent behavior, which an agent would benefit from knowing.

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

Parameters4/5

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

Schema coverage is 100% (baseline 3), and the description adds meaning beyond it by tying 'dependency' to the listAvailableDependencies output and clarifying that the optional version segment is normally supplied by Spring Boot.

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?

States a specific verb and resource ('Add an extra application dependency to the generated Maven or Gradle build') and clarifies scope with 'extra', separating it from dependencies Bootify adds automatically and from removeDependency. An agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives a clear prerequisite workflow: call listAvailableDependencies first, then pass the returned groupId:artifactId. It does not explicitly state exclusions (e.g., when to use removeDependency instead), so it falls just short of full when/when-not guidance.

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

All mcp tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?