[cli-tools-test] CLI bridge passes integer/boolean parameters as strings, breaking multiple tool filters

[github-actions]

Problem Description

The agenticworkflows MCP CLI bridge passes all parameter values as strings regardless of the schema type. This causes validation errors for integer and boolean parameters in the logs tool, making many filtering features completely unusable.

Affected Parameters

• count (integer) — Error: type: 3 has type "string", want "integer"
• max_tokens (integer) — Error: type: 3000 has type "string", want "integer"
• before_run_id (integer) — Error: type: 24613802341 has type "string", want "integer"
• after_run_id (integer) — same error
• filtered_integrity (boolean) — Error: type: true has type "string", want "boolean"
• firewall / no_firewall (boolean) — likely same error

Root Cause

The tools schema file at /home/runner/work/_temp/gh-aw/mcp-cli/tools/agenticworkflows.json is empty ([]). Since the bridge has no schema to reference, it cannot determine parameter types and passes all values as strings.

Steps to Reproduce

# Fails with: validating /properties/count: type: 3 has type "string", want "integer"
agenticworkflows logs --start_date "-1d" --count 3

# Fails with: validating /properties/before_run_id: type: 24613802341 has type "string", want "integer"  
agenticworkflows logs --start_date "-7d" --workflow_name "audit-workflows" --before_run_id "24613802341"

# Fails with: validating /properties/filtered_integrity: type: true has type "string", want "boolean"
agenticworkflows logs --start_date "-7d" --filtered_integrity true

Expected Behavior

The CLI bridge should coerce string values to their appropriate types (integer, boolean) based on the MCP tool schema from tools/list, so that --count 3 is sent as integer 3 and --filtered_integrity true is sent as boolean true.

Actual Behavior

All values are passed as strings, causing schema validation failures in the MCP server for any parameter typed as integer or boolean.

Secondary Issue: Tool Help Unavailable

agenticworkflows --help shows (tool list unavailable) because the tools JSON file is empty []. Users cannot discover available commands or their parameters.

Impact

• Severity: High
• Frequency: Always (affects all integer/boolean parameters)
• Workaround: Only use string-typed parameters (e.g., --workflow_name, --start_date, --engine)
• Blocked features: count limiting, before/after_run_id pagination, integrity filtering

Environment

• Repository: github/gh-aw
• Run ID: §24621812628
• Date: 2026-04-19
• Tools file: /home/runner/work/_temp/gh-aw/mcp-cli/tools/agenticworkflows.json (empty [])

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

• expires on Apr 26, 2026, 5:36 AM UTC