Skip to main content
Glama

SonarLint: status

sonarlint_status

Check whether the SonarLint engine is running, view the workspace root, and confirm the cached analyzer version.

Instructions

Report the state of the SonarLint engine: whether it is running, the workspace root, and the cached analyzer version.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

There are no annotations, so the description carries the full burden, and it does disclose the returned information (running flag, workspace root, analyzer version), which is the key behavioral fact for a zero-parameter status probe. It does not state whether querying status can start or block on the engine, what happens if the engine is stopped, or that the call is side-effect free — all relevant given no readOnlyHint.

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?

A single front-loaded sentence naming the resource first and the reported fields second, with no filler or redundant restatement of the title.

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

Completeness4/5

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

With no parameters, no annotations, and no output schema, the one-sentence enumeration of returned fields is essentially sufficient for an agent to call it correctly. Minor gaps remain around engine-start side effects and failure modes, which would matter for scripting status checks.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No misuse risk exists around arguments.

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

Purpose4/5

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

States a specific verb and resource ("Report the state of the SonarLint engine") and enumerates the three things reported: running state, workspace root, and cached analyzer version. That distinguishes it in substance from the scan_* and rules siblings, though it never names or contrasts 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 when-to-use guidance at all: nothing says to call this before scanning, to diagnose connection failures, or in what situation the workspace root/analyzer version matters. Usage is only inferable from the tool name.

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