Run PHP scripts inside the php-fpm container by specifying project directory, script path, and optional arguments for Magento 2 or RollDev environments.
Run a PHP script inside the php-fpm container
| Name | Required | Description | Default |
|---|---|---|---|
| args | No | Additional arguments to pass to the script | |
| script_path | Yes | Path to the PHP script relative to project root | |
| project_path | Yes | Path to the project directory |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description only states the action without disclosing any behavioral traits such as permissions, side effects, error handling, or output behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no wasted words, front-loaded. Could be slightly more descriptive but remains efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema and description does not hint at return values, errors, or execution context. Incomplete for a tool that runs arbitrary scripts.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and descriptions in the schema are clear. The tool description adds no extra meaning beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool runs a PHP script inside the php-fpm container, using a specific verb and resource, and distinguishes it from sibling tools like rolldev_magento_cli or rolldev_composer.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. Agent is not told when to prefer this over other script-running tools or context requirements.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.