[cli-tools-test] audit and compile MCP tools reject undocumented max_tokens parameter

[github-actions]

The audit and compile tools in the agentic-workflows MCP server reject max_tokens as an unknown parameter, yet the testing guidelines and workflow documentation instruct callers to always pass this parameter. This causes unexpected failures for anyone following the documented testing approach.

Reproduction

agenticworkflows audit --run_id_or_url 24761741707 --max_tokens 5000

Error:

{"error": "validating \"arguments\": validating root: unexpected additional properties [\"max_tokens\"]", "isError": true}

agenticworkflows compile --workflows "auto-triage-issues" --max_tokens 5000

Error:

{"error": "validating \"arguments\": validating root: unexpected additional properties [\"max_tokens\"]", "isError": true}

Expected Behavior

The max_tokens parameter should either be:

1. Accepted and respected — truncate/limit the response to the specified token count to keep downstream context windows bounded, OR
2. Documented as unsupported — the testing workflow documentation should be updated to remove references to max_tokens for audit and compile

Contrast: logs Tool

The logs tool does accept max_tokens without error (returns a file path with cached data). Only audit and compile reject it.

Impact

• Severity: Medium — any automated test or workflow that follows the documented max_tokens: 5000 guidance for audit/compile calls will fail entirely rather than return partial results
• Frequency: Always (100% reproducible)
• Workaround: Omit max_tokens from audit and compile calls

Environment

• Repository: github/gh-aw
• Run ID: §24761773317
• Date: 2026-04-22

References:

• §24761773317

Generated by Daily CLI Tools Exploratory Tester · ● 1.9M · ◷

• expires on Apr 29, 2026, 5:35 AM UTC

[pelikhan]

@copilot omit from all guidance, and ignore in audit, compile