getproblemsummary

Get problem summary with counts grouped by project and EDT severity level (ERRORS, BLOCKER, CRITICAL, MAJOR, MINOR, TRIVIAL). Use this for severity totals only; for the detailed per-marker list call get_project_errors.

Parameters

Parameter	Required	Type	Description
projectName	—	string	Name of the project (optional, all projects if not specified)

Guide

Validation problem COUNTS grouped by severity and by project - the at-a-glance health check. Returns a Markdown summary; for the actual per-problem messages, files and line numbers, use get_project_errors instead.

When to use

• A fast "is this project clean?" check, or to see where errors are concentrated before drilling in.
• After a clean / build / edit, to confirm the problem count went down.

Parameter details

• projectName - which project. Omit to summarize every project.

What you get

Markdown with an Overall Totals table (one row per severity - ERRORS, BLOCKER, CRITICAL, MAJOR, MINOR, TRIVIAL - plus a TOTAL) and, when more than one project is included, a By Project table with the same severity columns. When there are no problems it reports "No problems found."

Notes & gotchas

• Counts only - it never lists the individual problems. Follow up with get_project_errors for the detailed markers (file, line, message), or get_markers for bookmarks/tasks.
• The severities are EDT's own marker severities, not a simple error/warning split.

---

Generated from the live MCP server (get_tool_guide) by docs/generate_tool_docs.py. Do not edit this file. Edit the tool's description/schema in its Java source and its guide body in mcp/bundles/com.ditrix.edt.mcp.server/guides/<tool>.md.