mcp: fix DeleteInput.All type from *string to *bool

[thonmay]

Changes

Fixes a type mismatch in DeleteInput: the All field was typed as *string but the underlying func delete --all flag is a boolean cobra flag.

Problems with the old implementation:

• JSON schema presented string type to agents instead of bool
• appendStringFlag passed --all true (two args) instead of --all (one arg)
• Cobra's BoolVar would interpret true as a positional argument, not the flag value

Fix:

• All *string -> *bool
• appendStringFlag -> appendBoolFlag
• Updated jsonschema tag (removed redundant true/false hint)
• Updated test: moved all from stringFlags to boolFlags

/kind bug

Fixes #3706

Fix MCP `delete` tool: `all` parameter now correctly typed as bool

[knative-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: thonmay
Once this PR has been reviewed and has the lgtm label, please assign gauron99 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[knative-prow]

Hi @thonmay. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[thonmay]

Closing in favor of #3710 by @Elvand-Lie which was opened earlier and addresses the same issue.