Skip to main content
Glama
Sign In
Spring Toolkit MCP

Spring Toolkit MCP

by giaffa86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_flyway_status

Retrieve the current Flyway migration status from a Spring Boot application's Actuator endpoint to verify pending or applied migrations.

Instructions

Read /actuator/flyway runtime migration state.

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": "get_flyway_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, and the description only states 'Read', implying a safe operation, but does not disclose any side effects, authentication requirements, or what 'state' includes. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence), but it sacrifices important details. It could be expanded slightly to include parameter guidance or behavioral notes without losing conciseness.

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 low complexity (1 param, no output schema), the description is too minimal. It omits return value, error states, and relationship to sibling tools. Incomplete for a production tool.

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 single parameter 'application' has no schema description (0% coverage), and the description does not add any meaning beyond the parameter name. The agent cannot infer its purpose or format.

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 specifies the action (Read) and the resource (flyway migration state via actuator endpoint). It clearly identifies the tool's function, but does not explicitly differentiate from sibling 'inspect_flyway_migrations', which likely provides more detailed migration 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 on when to use this tool versus alternatives, such as 'inspect_flyway_migrations'. The description lacks context for selection.

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