Create Docker Compose templates for specified services, optionally including database services like PostgreSQL and Redis.
Generate a Docker Compose file template
| Name | Required | Description | Default |
|---|---|---|---|
| services | Yes | List of service names to include | |
| include_database | No | Include database services (PostgreSQL, Redis) |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description fails to disclose behavioral traits such as output format (file vs. string), side effects, prerequisites, or the nature of the generated template. This leaves significant ambiguity for an AI agent.
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?
The description is a single, concise sentence that front-loads the main action. However, it could be slightly expanded to include key details without becoming verbose.
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?
Given the absence of an output schema and annotations, the description should explain what the tool returns and how parameters affect the output. It fails to do so, leaving the agent without essential context for a simple but multi-parameter tool.
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?
The input schema provides clear descriptions for both parameters (services and include_database), achieving 100% schema coverage. The description adds no additional information beyond the schema, so baseline score of 3 is appropriate.
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?
The description clearly states the action 'Generate' and the resource 'Docker Compose file template', distinguishing it from sibling tools like 'docker_compose' and 'generate_dockerfile'. However, the term 'template' may introduce slight ambiguity regarding whether it produces a complete file or a template.
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 is provided on when to use this tool versus alternatives such as 'docker_compose' or 'generate_dockerfile'. The description lacks context for when generation is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.