[cli-tools-test] Parameter naming inconsistency between `logs` and `compile` MCP tools

[github-actions]

Problem Description

The logs and compile tools in the agentic-workflows MCP server use inconsistent parameter names for specifying workflow(s), which causes agent confusion and tool call failures.

Command/Tool

• Tool: logs and compile
• Parameter: workflow filtering

Steps to Reproduce

1. Observe logs tool help: --workflow_name (string, singular)
2. Observe compile tool help: --workflows (array, plural)
3. Try calling compile with --workflow_name daily-fact (natural assumption from logs API)
4. Receive confusing error: Unknown parameter 'workflow_name'. Did you mean 'workflows'?

# logs uses --workflow_name (string)
agenticworkflows logs --workflow_name "daily-fact" --count 3

# compile uses --workflows (array)
printf '{"workflows":["daily-fact"]}' | agenticworkflows compile .

Expected Behavior

Both tools should use a consistent parameter name and type. Either:

• Both accept --workflow or --workflow_name as a string
• Both accept --workflows as an array (with single-string coercion)

Actual Behavior

• logs uses --workflow_name (string)
• compile uses --workflows (array)
• Passing --workflow_name to compile produces an error suggesting --workflows, which then requires array syntax

Environment

• Repository: github/gh-aw
• Run ID: 26495176905
• Date: 2026-05-27

Impact

• Severity: Medium
• Frequency: Always — affects all agents/users switching between the two tools
• Workaround: Check --help for each tool individually and remember distinct parameter names

Additional Context

This was discovered during daily exploratory testing. The error message (Did you mean 'workflows'?) is helpful but the inconsistency itself causes unnecessary friction. A consistent interface would allow agents to use the same mental model across both tools.

Generated by 🧪 Daily CLI Tools Exploratory Tester · sonnet46 2.6M · ◷

• expires on Jun 3, 2026, 6:48 AM UTC