The query parameter issue is a pattern I see a lot. The model has thousands of examples of "how HTTP requests usually look" from its training process. When your input data conflicts with the pattern, the training data takes precedence.

Interestingly, the model doesn't "know" that it's ignoring you. From its perspective, it has retrieved a "meaningful" pattern—virtual parameter names that probably fit common conventions it saw during training. Your actual request simply... wasn't documented.