diagnostic_hotspots
[diagnostics]
Groups TypeScript and JavaScript diagnostics by file, project, category, or code for compact triage.
Try it locally in the TGlider playground
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| filePath | string | No | Workspace-relative or absolute file path. |
| projectName | string | No | Optional loaded project name to scope the query. |
| severity | string | No | Filter by 'all', 'error', 'warning', 'suggestion', or 'message'. Default: "all" |
| diagnosticCodes | json | No | Optional array of TypeScript diagnostic codes. |
| includeDeclarationFiles | boolean | No | Include diagnostics from declaration files. Default: false |
| includeGenerated | boolean | No | Include diagnostics from generated-looking files. Default: false |
| groupBy | string | No | Group by 'file', 'project', 'category', or 'code'. Default: "file" |
| exampleTake | number | No | Maximum diagnostic examples to include per group. |
| skip | number | No | Number of matching results to skip. Default: 0 |
| take | number | No | Maximum number of matching results to return. |
Examples
Replace sample paths and symbol keys with values from your workspace.
Group diagnostics by project
Arguments
{
"groupBy": "project",
"severity": "error"
}Full MCP request
Full MCP request
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "diagnostic_hotspots",
"arguments": {
"groupBy": "project",
"severity": "error"
}
}
}Response Notes
Returns grouped diagnostic counts and examples, with inferred-project labeling (scope.inferred, inferredProjectCount, notes) when diagnostics may be incomplete.