Controls local Microsoft Project via COM automation
MS Project MCP exhibits significant gaps in definition quality. Tools are properly named with action verbs (open_, new_, get_, set_), but descriptions lack sufficient context for LLM selection and parameter descriptions are sparse or missing entirely. The server operates on a Windows-only desktop application via COM automation, which introduces environmental constraints not surfaced in tool documentation. Input schemas are present but incomplete, most parameter descriptions are minimal. Output schemas are partially documented via code comments (task_to_dict function) but not formally declared in tool signatures. Error handling provides no recovery guidance; most error cases raise RuntimeError with generic messages. Security critical: the server requires Windows COM interop with no parameterized secrets, but tool definitions expose no credentials in parameters directly.
Get summary information about the currently active project.
Create a new blank project without needing a file on disk.
Open a Microsoft Project file (.mpp or .xml). MS Project must already be running (it is launched automatically if not).
Set project metadata properties.
Output schemas not documented in tool definitions. Tools return JSON structures (open_project returns status, name, full_path, task_count, start, finish; new_project returns status, title, name, start; get_project_info return structure is not visible in excerpt) but no @mcp.tool() decorator includes a returns= or output schema specification. LLMs cannot predict downstream tool chains without knowing what fields are available.
Parameter descriptions are minimal or missing actionable constraints. 'file_path' lacks format guidance (must be .mpp or .xml per docstring, but not in param description). 'start' describes format but not required/optional status. 'properties_json' forces raw JSON construction, violating the chat-data-model pattern, LLMs struggle with JSON string assembly and misformat payloads.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
Error handling provides no recovery guidance. Tools raise generic RuntimeError ('MS Project is not running'; 'No project file is open') without actionable next steps. LLMs cannot self-correct or suggest alternatives. Per pattern:recovery-guide, errors should state 'What failed?' and 'What should I try next?'
Tool descriptions lack context for selection. 'Get summary information' is vague; 'Create a new blank project' doesn't clarify how it differs from open_project; 'Open a Microsoft Project file' doesn't explain when this is preferred over new_project. Per pattern:tool-description, each should answer WHAT, WHEN, and prerequisites.
set_project_properties uses a single 'properties_json' string parameter instead of typed parameters (title, manager, company, author, subject, status_date, start). This violates composition patterns: forces LLMs to construct raw JSON, prevents validation before submission, and defeats type-checking. Solution: accept individual typed parameters.
No idempotency guidance. open_project and new_project perform side effects (launch application, open files, create projects) but do not declare idempotent hints or acknowledge retry implications. Per pattern:idempotent-operation, repeated calls with identical input should produce the same state or fail safely. Current implementation may create duplicate projects or fail unpredictably on retry.
Environmental and platform constraints not surfaced in tool definitions. Server requires Windows, COM automation, and local MS Project installation. None of these are documented as prerequisites or declared in tool descriptions. LLMs on non-Windows systems or without MS Project will invoke tools that cannot succeed.