SonarRemedy

sonar_remedy_run

Process a bounded manual batch of SonarQube fix proposals, enabling controlled technical debt recovery with options to limit, resume, or execute.

Instructions

Lease/process a bounded manual proposal batch.

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": {
      "state": "<state>"
    },
    "name": "sonar_remedy_run"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`state`	Yes
`resume`	No
`execute`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 18, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'lease/process' but does not explain side effects, whether the operation is idempotent, what 'bounded' means, or what happens on execution. The boolean 'execute' parameter hints at a dry-run vs. execution mode, but the description does not clarify this.

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 short sentence, which is concise, but it is under-specified rather than efficiently informative. It front-loads the action but omits essential context that would make the sentence useful.

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 four parameters, no annotations, no output schema, and a terse description, the tool definition is incomplete. An agent cannot reliably determine how to invoke this tool correctly, what the parameters mean, or what the outcome will be.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for the four undocumented parameters. It does not explain 'state', 'limit', 'resume', or 'execute' beyond their names. The term 'bounded' loosely maps to 'limit', but no concrete semantics are provided.

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?

The description 'Lease/process a bounded manual proposal batch' identifies a specific action (lease/process) and resource (a bounded manual proposal batch), which is more than a tautology. However, it does not distinguish this tool from siblings like sonar_remedy_run_all or sonar_remedy_slice, and the meaning of 'lease/process' is ambiguous without further context.

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 tool versus alternatives such as sonar_remedy_run_all or sonar_remedy_schedule. The description implies a manual batch operation but does not state conditions, prerequisites, or exclusions, leaving the agent to guess.

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

Deploy Server