MCP Server for installing and setting up PHP Composer packages with AI assistants
Single tool with basic schema and description. Tool name 'install_package' follows verb_noun convention (+). Input schema present with Zod types and descriptions (+). However, description is generic (67 chars, below 194-char baseline), lacks WHEN/WHY guidance, and does not clarify that this tool only provides instructions rather than executing installation. No output schema documented. No error handling guidance. No parameter constraints (e.g., valid package name format). Tool does not actually execute commands, it returns text instructions, which is a critical mismatch with the tool's implied semantics. This creates high risk of LLM misuse.
Install a Composer package with optional version specification and automatic setup step detection
Tool description does not clarify that install_package returns instructions only, not actual installation. LLMs will expect the tool to execute composer require, leading to misuse.
No output schema documented. LLMs cannot predict the response structure (text content, setup steps format, error format). Baseline: 100% of A+ tools document return types.
Description is 67 characters (below 194-char baseline). Lacks WHEN to use, prerequisites, and consequences. Does not explain that setup steps are auto-detected from README or hardcoded fallbacks.
No input validation or constraints. 'package' parameter accepts any string; no regex pattern, length limit, or format guidance. LLMs may pass invalid package names (spaces, special chars, etc.).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Error handling returns plain text errors without recovery guidance. E.g., 'Error: ...' gives LLM no actionable next step. Should indicate whether error is retryable or user-fixable.