SonarRemedy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GIT_PAT | Yes | Git personal access token for repository access | |
| SONAR_TOKEN | Yes | SonarQube authentication token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sonar_remedy_fetchC | Fetch Sonar issues for a project into an export (chunked if over budget). |
| sonar_remedy_sliceC | Create a durable queue from an export. |
| sonar_remedy_runC | Lease/process a bounded manual proposal batch. |
| sonar_remedy_statusC | Report the queue's next action and ETA. |
| sonar_remedy_progressD | Write a human-readable progress file. |
| sonar_remedy_scheduleC | Show the parallel/serial plan for pending jobs. |
| sonar_remedy_run_allD | Fetch + slice every chunk into its own queue. |
| sonar_remedy_analyzeC | Run the local pipeline to regenerate+publish Sonar results. |
| sonar_remedy_integrateC | Serially apply a recorded proposal and run bound checks. |
| sonar_remedy_configureC | Bind reviewed check commands and the current target snapshot. |
| sonar_remedy_projectsA | List saved project configs. |
| sonar_remedy_configure_projectB | Save a project's Sonar/repo config non-interactively. The token is NOT stored here — the user sets SONAR_TOKEN separately (masked). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools target distinct workflow stages, but run_all is misleading (it actually fetches and slices rather than running all processing) and status/schedule overlap somewhat. Descriptions are clear enough to resolve most ambiguity.
All tools share the consistent sonar_remedy_ prefix and snake_case style, which is predictable. However, suffixes mix plain verbs (fetch, slice, integrate) with nouns (projects, status, progress) and verb+object (configure_project), so the pattern is not fully uniform.
Twelve tools cover a multi-stage Sonar remediation workflow without feeling bloated. Each tool maps to a meaningful operation or report, and the count is well-scoped for the domain.
The set covers configuration, fetching, queueing, processing, integration, analysis, and status reporting for the remediation pipeline. Minor lifecycle operations such as explicitly deleting/resetting a queue or updating a saved project config are absent but workaroundable.