MCP server for Composer package management and project maintenance via AI assistance
The server has 5 tools with explicit registration via #[McpTool] attributes and proper schema annotations via #[Schema]. Tool names follow verb_noun convention (search_packages, get_package_info, read_composer_json, analyze_project, suggest_upgrades). All tools have descriptions present and most parameters have type definitions and constraints. However, output schemas are not documented in the code, return types are declared as PHP type hints (array, mixed) but the structure and fields are not explicitly documented for LLMs. Error handling is present with specific exceptions but lacks recovery guidance. No tool annotations for destructiveness or idempotency. Parameter descriptions are present but some lack detail about format/constraints. The rubric baseline for A+ tools requires documented return types (100% of A+ tools have these), output field documentation, and comprehensive parameter guidance. This server meets ~60% of those requirements.
Analyze a Composer project for issues and improvements
Get detailed information about a PHP composer package
Read and parse a composer.json file
Search for PHP composer packages on Packagist.org
Suggest available package upgrades for a project
Output schemas not documented. Tools return array<mixed> or array<...> but LLMs cannot infer the structure, field names, and types of the response. This violates the D.SCHEMAS & OUTPUT requirement that every tool must document its return type.
No tool annotations present. Tools lack readOnlyHint, destructiveHint, and idempotentHint attributes. All 5 tools are READ_ONLY but this is not declared in the tool definitions via annotations, the LLM must infer it from descriptions.
Error responses lack recovery guidance. readComposerJson() and analyzeProject() throw exceptions with basic messages ('File not found', 'Project directory not found') but do not guide the LLM on what to do next (e.g., 'Try search for available projects using get_package_info').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 53 | 2026-07-28+ | v2 |
Parameter descriptions lack detail on constraints and format. Example: get_package_info's 'packageName' parameter has a regex pattern in the schema but the description does not explain the format. read_composer_json's 'path' accepts 'Absolute path' but does not clarify whether it must be a composer.json file specifically or any file.
analyze_project and suggest_upgrades accept 'projectPath' as a string without validation hints. The description says 'Path to the project directory' but does not warn that it must contain composer.json or clarify what happens if it does not.