Problem Description
When calling the compile MCP tool with actionlint: true or poutine: true in an environment where Docker is not available, the error message instructs users to "omit the --actionlint flags". However, in the MCP interface, these are boolean parameters — not CLI flags. This causes confusion because the remediation guidance doesn't match the interface the user is working with.
Tool
- Tool:
compile (agentic-workflows MCP server)
- Parameters used:
actionlint: true
Steps to Reproduce
- Call the
compile MCP tool with actionlint: true in an environment without Docker:
{ "workflows": ["auto-triage-issues"], "actionlint": true }
- Observe the error message returned.
Expected Behavior
The error message should reference MCP parameters, not CLI flags. For example:
docker is not available (cannot connect to Docker daemon). actionlint requires Docker. Please install and start Docker, or set actionlint: false to skip static analysis.
Actual Behavior
McpError: MCP error -32603: calling "tools/call": docker is not available (cannot connect to Docker daemon).
actionlint requires Docker. Please install and start Docker, or omit the --actionlint flags
The message says --actionlint flags which implies a CLI invocation style. An MCP user has no --actionlint flag to omit — they have a actionlint boolean parameter.
Environment
- Repository: github/gh-aw
- Run ID: §23729320081
- Date: 2026-03-30
- Context: Agentic environment (Docker-in-Docker not supported)
Impact
- Severity: Low
- Frequency: Always (in Docker-unavailable environments)
- Workaround: Set
actionlint: false (omit the parameter) and poutine: false
Additional Context
The same issue likely affects the poutine: true parameter since it also requires Docker. The fix should update the error message to use parameter/option terminology consistent with MCP usage rather than CLI flag syntax.
References:
Generated by Daily CLI Tools Exploratory Tester · ◷
Problem Description
When calling the
compileMCP tool withactionlint: trueorpoutine: truein an environment where Docker is not available, the error message instructs users to "omit the--actionlint flags". However, in the MCP interface, these are boolean parameters — not CLI flags. This causes confusion because the remediation guidance doesn't match the interface the user is working with.Tool
compile(agentic-workflows MCP server)actionlint: trueSteps to Reproduce
compileMCP tool withactionlint: truein an environment without Docker:{ "workflows": ["auto-triage-issues"], "actionlint": true }Expected Behavior
The error message should reference MCP parameters, not CLI flags. For example:
Actual Behavior
The message says
--actionlint flagswhich implies a CLI invocation style. An MCP user has no--actionlintflag to omit — they have aactionlintboolean parameter.Environment
Impact
actionlint: false(omit the parameter) andpoutine: falseAdditional Context
The same issue likely affects the
poutine: trueparameter since it also requires Docker. The fix should update the error message to use parameter/option terminology consistent with MCP usage rather than CLI flag syntax.References: