Skip to main content
Glama

Opsphere — DevOps & SRE Intelligence

SonarQube security hotspots search

sq_hotspots_search
Read-only

List security hotspots pending review for a project.

Input Schema

NameRequiredDescriptionDefault
pageNo
branchNo
statusNoHotspot review status filter
projectYesSonarQube project key, SonarCloud org_project key (e.g. cepsadigital_my-repo), or sonarcloud.io overview URL
pageSizeNo
context_idNoOptional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.

Output Schema

NameRequiredDescriptionDefault
okYes
dataYes
contractVersionYes
dataSchemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changed
    • changedOutput schema / properties / data / additionalProperties
      Previous value: -trueNew value: +false
    • removedOutput schema / properties / data / properties / analyses
      Removed value: -{
      -  "$ref": "#/properties/data/properties/projects"
      -}
    • removedOutput schema / properties / data / properties / branches
      Removed value: -{
      -  "$ref": "#/properties/data/properties/projects"
      -}
    • removedOutput schema / properties / data / properties / count
      Removed value: -{
      -  "type": "number"
      -}
    • removedOutput schema / properties / data / properties / duplications
      Removed value: -{
      -  "$ref": "#/properties/data/properties/projects/items"
      -}
    • addedOutput schema / properties / data / properties / family
      Added value: +{
      +  "const": "sonarqube",
      +  "type": "string"
      +}
    • addedOutput schema / properties / data / properties / gaps
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / data / properties / issues
      Removed value: -{
      -  "$ref": "#/properties/data/properties/projects"
      -}
    • removedOutput schema / properties / data / properties / measures
      Removed value: -{
      -  "$ref": "#/properties/data/properties/projects"
      -}
    • addedOutput schema / properties / data / properties / operation
      Added value: +{
      +  "const": "sq_hotspots_search",
      +  "type": "string"
      +}
    • addedOutput schema / properties / data / properties / partial
      Added value: +{
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / data / properties / project
      Removed value: -{
      -  "$ref": "#/properties/data/properties/projects/items"
      -}
    • removedOutput schema / properties / data / properties / projects
      Removed value: -{
      -  "items": {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • removedOutput schema / properties / data / properties / pullRequests
      Removed value: -{
      -  "$ref": "#/properties/data/properties/projects"
      -}
    • removedOutput schema / properties / data / properties / qualityGate
      Removed value: -{
      -  "$ref": "#/properties/data/properties/projects/items"
      -}
    • addedOutput schema / properties / data / properties / records
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "assignee": {
      +        "type": "string"
      +      },
      +      "body": {
      +        "type": "string"
      +      },
      +      "component": {
      +        "type": "string"
      +      },
      +      "createdAt": {
      +        "type": "string"
      +      },
      +      "environment": {
      +        "type": "string"
      +      },
      +      "facts": {
      +        "items": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "name": {
      +              "type": "string"
      +            },
      +            "value": {
      +              "anyOf": [
      +                {
      +                  "type": "string"
      +                },
      +                {
      +                  "type": "number"
      +                },
      +                {
      +                  "type": "boolean"
      +                },
      +                {
      +                  "type": "null"
      +                },
      +                {
      +                  "items": {
      +                    "type": [
      +                      "string",
      +                      "number",
      +                      "boolean",
      +                      "null"
      +                    ]
      +                  },
      +                  "type": "array"
      +                }
      +              ]
      +            }
      +          },
      +          "required": [
      +            "name",
      +            "value"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "key": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "priority": {
      +        "type": "string"
      +      },
      +      "project": {
      +        "type": "string"
      +      },
      +      "qualityGate": {
      +        "type": "string"
      +      },
      +      "reporter": {
      +        "type": "string"
      +      },
      +      "rule": {
      +        "type": "string"
      +      },
      +      "status": {
      +        "type": "string"
      +      },
      +      "summary": {
      +        "type": "string"
      +      },
      +      "tags": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "type": "string"
      +      },
      +      "updatedAt": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "facts"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / data / properties / summary
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / data / properties / total
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / data / properties / truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / data / properties / warnings
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / data / required
      Added value: +[
      +  "family",
      +  "operation",
      +  "records",
      +  "total",
      +  "partial",
      +  "truncated",
      +  "warnings",
      +  "gaps"
      +]
    • addedOutput schema / properties / dataSchemaVersion
      Added value: +{
      +  "const": 2,
      +  "type": "number"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "contractVersion",
      -  "ok",
      -  "data"
      -]New value: +[
      +  "contractVersion",
      +  "dataSchemaVersion",
      +  "ok",
      +  "data"
      +]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds the useful behavioral fact that the default view is 'pending review' hotspots, but that framing arguably conflicts with the status parameter that allows REVIEWED, and it says nothing about pagination behavior via page/pageSize.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero waste. It is efficient, though it errs toward under-specification rather than conciseness for a tool with six parameters.

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?

An output schema exists so return values need not be explained, but the description omits pagination semantics, branch handling, and the meaning of the status filter, all of which matter for a six-parameter listing tool. For a tool at 50% schema coverage, this leaves too much for the agent to infer.

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 50%: project and context_id are documented in the schema, but page, pageSize, branch, and status have no descriptions. The description only references the project scope and implies a status filter; it does not explain paging limits (pageSize max 500), default ordering, or branch targeting, so it fails to compensate for the coverage gap.

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?

The description states a specific verb and resource ('List security hotspots') scoped to a project, so the agent knows exactly what the tool returns. However, 'pending review' is narrower than what the tool actually does, since the status enum also permits REVIEWED, leaving the stated scope slightly misleading. No sibling hotspot tool exists to differentiate against, which caps the score at 4.

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?

The description gives no guidance on when this tool should be chosen over alternatives, nor any prerequisites such as authentication or required project key resolution. There is no mention of when-not-to-use or of the reviewed-status variant, so the agent must infer usage entirely from the name and schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources