Appearance
in-Plug-in overview
Models have limitations: they cannot access the latest information, are prone to hallucination, and struggle with precise calculations. Integrate plugins to address these limitations.
Introduction to plugins
A plugin is a collection of tools (APIs), each implementing a specific capability. Model Studio supports official plugins and custom plugins.
Official plugins
The Plug-in Marketplace offers pre-configured official plugins that you can call without setup. See Official plugin instructions.
| Plugin name | Tool ID | Description | Billing |
|---|---|---|---|
| Python Code Interpreter | code_interpreter | Enables the model to execute Python code for tasks such as mathematical calculations, data analysis and visualization, and data processing. | Free |
| Calculator | calculator | Enables the model to perform complex mathematical calculations, such as "12313*13232". | Free |
| Image Generation | text_to_image | Enables the model to generate images from text, such as "Draw a smiling dog." | Free for a limited time, activation required. |
Custom plugins
You can create custom plugins and integrate them into your application.
Examples
| Sample input | Without plugin | With plugin |
|---|---|---|
| What is 12313 × 13232? | A model cannot reliably solve complex math problems and often returns incorrect answers. The correct answer is 162,925,616. | With the Calculator plugin, the model performs the calculation accurately. |
Supported models
| Model | Model identifier |
|---|---|
| Qwen-Turbo | qwen-turbo |
| Qwen-Plus | qwen-plus |
| Qwen-Max | qwen-max |
| Qwen-VL-Max | qwen-vl-max |
| Qwen-VL-Plus | qwen-vl-plus |
Note
Plugin compatibility varies by model. Check the console for details.
See Select a model.
How plugins work
Calling a plugin means calling a tool within it. You can call plugins through an agent application or a workflow application.
When a plugin is called from an agent application, the model determines whether to call a tool based on the user input , tool name , and tool description.
If a tool is required, the model selects the appropriate one. The application then calls the tool, combines its output with the original user input, and sends the result back to the model to generate the final response.
If no tool is required, the model generates the final response directly.
In a workflow application, calling a plugin means using it as a node in the workflow. The tool is executed as part of a user-defined sequence, rather than the model selecting and calling it autonomously.