Skip to main content
Glama
Sign In
spring-mosaic

spring-mosaic

by himakarinv-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

detect_spring_context

Identifies Spring Boot version, Java version, build tool, and modules in a project. Use as the initial step for analysis.

Instructions

Detect Spring Boot / Java version, build tool, and modules. Call first.

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

Input Schema

NameRequiredDescriptionDefault
workspaceRootNoProject root (default: cwd)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description must carry the full burden. The description implies a read-only detection operation but does not explicitly state safety (e.g., no side effects). Lacks details on permissions or impact.

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?

Two sentences, no filler, front-loaded with action. Every word earns its place.

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?

While the tool's purpose is clear, it lacks description of output format or how results feed into sibling tools. Given no output schema, the description should provide more context on what the agent receives after calling.

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 coverage is 100% for the single parameter. Description adds no additional meaning beyond the schema's description of 'workspaceRoot'.

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?

Description states specific verb 'Detect' and specific resources: Spring Boot / Java version, build tool, and modules. The instruction 'Call first' further clarifies its role. Sibling tools are quality/review tools, making this distinct.

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?

Explicitly says 'Call first,' indicating it should be used before other sibling tools. No alternative tools or when-not-to-use guidance provided, but the context is clear.

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