Doc bug in Kiro power POWER.md - search_sonar_issues_in_projects example uses parameter names the MC

Environment

  • SonarQube Server or Cloud? SonarQube Server
  • Deployment type (STDIO/HTTP, Docker/JAR): STDIO, Docker image (sonar run mcp, SonarQube CLI 1.7.0)
  • Client / AI tool using MCP (if applicable): Kiro (Kiro power for SonarQube)

Description

The POWER.md in SonarSource/sonarqube-agent-plugins has an example that doesn’t validate against the actual MCP tool schema. Reporting here since Issues are disabled on the repo.

File: POWER.md (also shipped in the installed Kiro power) Location: the “Filter issues effectively” example, around lines 108–116.

Current example:

Two parameter names don’t match the search_sonar_issues_in_projects tool schema:

  • projects → the schema defines projectKeys
  • p / ps → the schema defines pageIndex / pageSize

Calling the tool with the parameters as written fails schema validation:

Suggested fix:

The dependency-risks example later in the same file (around lines 302–303) already uses pageIndex/pageSize correctly, so this is an internal inconsistency — the issue-search example just needs to match. The search_my_sonarqube_projects example earlier in the file has the same p/ps → pageIndex/pageSize issue and would be worth correcting in the same pass.

Hey @Jerry_Drumm, great catch! I’m doing a full review of the repository and I will fix all the discrepancies. Over time, some of the instructions may have drifted a bit, we will try to keep them thoroughly in sync.