Allow Preconfiguration of Parameters in MCP for Standalone Tools

Currently, users can preconfigure parameters when connecting MCP to a workflow. However, this capability is missing when tools are connected directly to MCP.

As a result, every time a standalone MCP tool is called, users must manually provide all input parameters — including long strings, UUIDs, and other repetitive identifiers. This creates unnecessary friction, especially for tools that require complex or lengthy inputs.

Adding support for preconfigured parameters at the tool level (outside of workflows) would significantly improve usability and reduce manual errors.