diagnostic_hotspots

[diagnostics]

Groups diagnostics into hotspots by file, project, category, or ID so you can plan cleanup before drilling into raw diagnostics.

Try it locally in the Glider playground

Parameters

Name	Type	Required	Description
filePath	string	No	Optional file path filter.
projectName	string	No	Optional project name filter.
diagnosticSource	string	No	Diagnostic source: 'compiler' (default), 'all', or 'analyzer'. Default: `"compiler"`
severity	string	No	Minimum severity: 'error', 'warning', 'info', or 'hidden'. Default is 'warning'. Default: `"warning"`
category	string	No	Optional category filter (e.g., 'Compiler', 'Style').
idPrefix	string	No	Optional diagnostic ID prefix filter (e.g., 'CS', 'CA', 'IDE').
groupBy	string	No	Primary grouping: 'file' (default), 'project', 'category', or 'id'. Default: `"file"`
includeExamples	boolean	No	Include example diagnostics inside each hotspot group. Default is false. Default: `false`
maxExamplesPerGroup	number	No	Maximum example diagnostics to include per group when includeExamples=true. Default is 3. Use 0 for none. Default: `3`
pathStyle	string	No	Path style: 'absolute' (default) or 'relative' (to solution root). Default: `"absolute"`
sortBy	string	No	Optional sort: 'count' (default), 'errorCount', 'warningCount', 'infoCount', or 'key'.
sortOrder	string	No	Sort order: 'desc' (default) or 'asc'. Default: `"desc"`
skip	number	No	Pagination offset. Default is 0. Default: `0`
take	number	No	Pagination size. Default is 50. Default: `50`
responseDetail	string	No	compact returns results and actionable state. full adds diagnostic metadata under responseDiagnostics. Default: `"compact"`

Examples

Replace sample paths and symbol keys with values from your workspace.

Group compiler diagnostics by file

Arguments 
{
  "groupBy": "file"
}

Full MCP request

Full MCP request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "diagnostic_hotspots",
    "arguments": {
      "groupBy": "file"
    }
  }
}

Illustrative response 
{
  "success": true,
  "restoreHints": [],
  "restoreHintsOmittedProjectCount": 0,
  "restoreHintsNextStep": null,
  "groupBy": "file",
  "groupCount": 1,
  "paging": {
    "total": 1
  },
  "comReferenceHints": [],
  "groups": [
    {
      "key": "/path/to/UserService.cs",
      "totalCount": 4,
      "errorCount": 1,
      "warningCount": 3,
      "infoCount": 0,
      "examples": [
        {
          "id": "CS8602",
          "severity": "Warning",
          "lineNumber": 42,
          "message": "Dereference of a possibly null reference."
        }
      ]
    }
  ]
}

Show analyzer hotspots with examples

Arguments 
{
  "diagnosticSource": "analyzer",
  "groupBy": "category",
  "includeExamples": true
}

Full MCP request

Full MCP request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "diagnostic_hotspots",
    "arguments": {
      "diagnosticSource": "analyzer",
      "groupBy": "category",
      "includeExamples": true
    }
  }
}

Response Notes

Returns grouped diagnostics with severity totals and optional examples. comReferenceHints identifies missing COM wrappers and the build or reload remedy. Analyzer-only responses have no restore hints. restoreHints lists up to 20 projects with relevant compiler errors, diagnosticIds, unverified restoreState, and restore/build plus reload advice. restoreHintsOmittedProjectCount and restoreHintsNextStep explain how to request omitted projects with projectName. Glider preserves compiler errors and does not run restore or infer restore state from asset paths or timestamps. Results use top-level fields with success. Compact is the default; full adds responseDiagnostics. Both modes retain errors, coverage, partial state, and recovery advice.