Skip to main content
Glama
Sign In
spring-mosaic

spring-mosaic

by himakarinv-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

review_pr_diff

Orchestrate PR reviews by analyzing changed files, their extensions, and defining review steps for Java/Spring Boot projects.

Instructions

PR review orchestration: changed files, extensions, and review steps.

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": {
      "changedFiles": "<changedFiles>"
    },
    "name": "review_pr_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
changedFilesYes
workspaceRootNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are provided. The description says 'orchestration' but does not disclose whether the tool is destructive, requires authentication, modifies state, or has side effects. With zero annotations, the description carries the full burden, and it fails to provide any behavioral insight.

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 a single sentence, making it concise, but it is vague and does not earn its place fully. It could be restructured to include key information without being longer.

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

Completeness1/5

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

Given the tool has no output schema, no annotations, and two parameters, the description is severely incomplete. It does not explain return values, behavior, or usage steps. The agent would struggle to use this tool correctly.

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 input schema has two parameters (changedFiles, workspaceRoot) with 0% schema description coverage. The tool description does not add any meaning beyond their names. It does not clarify expected format, purpose, or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'PR review orchestration: changed files, extensions, and review steps.' It is somewhat specific about the components but vague on what the tool actually does or returns. Sibling tools like 'get_pr_review_brief' and 'get_review_sections_for_diff' suggest a range of PR review actions, and this description does not sufficiently distinguish them.

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 provided on when to use this tool versus the many sibling tools. The description does not mention prerequisites, alternatives, or context. It leaves the agent to infer usage.

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