Skip to main content
Glama
Sign In
Spring Toolkit MCP

Spring Toolkit MCP

by giaffa86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

generate_mockmvc_test

Generate MockMvc tests for Spring controllers in a project directory. Optionally specify a controller class to focus on.

Instructions

Alias for spring_generate_mockmvc_tests.

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

Input Schema

NameRequiredDescriptionDefault
pathNoProject directory to inspect.
controllerNoOptional controller class name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits of the tool (e.g., what it creates, side effects, permissions needed). The agent cannot infer behavior without relying on the aliased tool's separate definition.

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?

The description is a single sentence that directly states the tool's nature as an alias. It is concise and front-loaded, with no unnecessary words.

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?

As an alias with no output schema and minimal description, the agent cannot fully understand the tool's behavior without consulting the aliased tool's definition. The context signals show siblings but do not compensate for the lack of behavioral and usage details.

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% with clear parameter names and descriptions. The description adds no additional meaning beyond what the schema already provides, so baseline of 3 is appropriate.

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?

Description explicitly states it is an alias for spring_generate_mockmvc_tests, making the tool's purpose clear as a shortcut. It identifies the verb 'generate' and resource 'mockmvc tests', but does not elaborate further. It is distinct from siblings by being an alias.

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 alias vs the original spring_generate_mockmvc_tests or other siblings. The description does not mention prerequisites, alternatives, or exclusions.

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