Skip to main content
Glama
GleisonOliveira

php-container-test-mcp

Run All PHP Tests

run_php_tests

Run the full PHP test suite inside a Docker container to validate code changes and ensure all tests pass.

Instructions

ALWAYS use this tool to run the full PHP test suite inside a Docker container — never run composer or phpunit directly on the host. Use when the user says: run tests, run all tests, run unit tests, run integration tests, execute tests, check if tests pass, make sure nothing broke, validate the feature, verify the fix, rodar testes, rodar todos os testes, executar testes, verificar se os testes passam. Returns the full test output (stdout + stderr) so you can evaluate pass/fail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandNoComposer script to run (e.g. "test", "test:unit"). Defaults to "test".
host_pathNoAbsolute path to the project on the host. Defaults to the server argument or current working directory.
container_nameYesDocker image name (e.g. "my-php-app:latest").
container_pathNoMount path inside the container. Defaults to the server argument or "/var/www".
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description covers main behavior (runs tests in container, returns full output) but misses prerequisites like Docker being installed and potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with key instruction, but the long list of trigger phrases could be condensed; overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a test runner with 4 params and no output schema, the description covers purpose, usage, and output; missing hints about Docker availability and error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description adds limited value beyond defaults; it restates default command as 'test' but doesn't deeply explain all parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it runs the full PHP test suite inside a Docker container, distinguishing from host commands and sibling 'run_php_test_file' by emphasizing 'full' suite.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit trigger phrases and warns against direct host commands, but does not contrast with the sibling tool for running single test files.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GleisonOliveira/php-container-test-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server