Filesystem MCP

compose_config

Read-onlyIdempotent

Render and validate Docker Compose configuration files to catch errors and produce resolved YAML before deployment.

Instructions

Render and validate compose configuration (docker compose config).

Args: See Parameters block.

Return Format

{"success": bool, "action": str, "message": str, "result": {"output": str, "stderr": str}} result.output: rendered YAML.

Examples

compose_config(path="D:/dev/myapp") compose_config(path="D:/dev/myapp", validate=False)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compose_config"
  }
}

Input Schema

Name	Required	Default
`path`	No	.
`timeout`	No
`validate`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.1.0Oct 25, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that stderr is captured and returned in a structured envelope, which hints at failure visibility, but it never says what happens when validation fails (success=false? exception?) — despite an output schema already documenting the response shape.

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

Conciseness3/5

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

The purpose line is front-loaded and the examples are compact and useful, but "Args: See Parameters block." is a zero-information sentence and the Return Format block largely restates an output schema that already exists. Roughly a third of the text does not earn its place.

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

Completeness2/5

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

For a tool whose parameters are entirely undocumented, the description should carry the load and does not: path semantics, timeout behavior, and the effect of validate=true are all left to guesswork. The examples and return envelope are helpful, but an agent still cannot confidently predict what validation means here.

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

Parameters2/5

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

Schema description coverage is 0% — all three parameters have only types and defaults. The description deflects with "See Parameters block" and then provides no meaning for `timeout` at all, and no explanation of what `validate` toggles or whether `path` is a directory or a compose file. The two examples only weakly illustrate `path` and `validate=False`.

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

Purpose4/5

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

The description names a specific verb pair and resource ("Render and validate compose configuration") and anchors it to the real command "docker compose config". That distinguishes it from sibling compose tools like compose_up/compose_down/compose_logs, though it never explicitly states that it does not start containers.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives (e.g. use compose_up to actually launch), and no prerequisites. "Args: See Parameters block." is the only nod to usage, and the examples show call shapes rather than decision criteria.

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