Creating a Function Tool
Follow these steps to create a new Function ToolAdd a new Tool to a Project
+ button to add a new Entity to a Project.
Enter Tool Details
- Key, used by models to reference the tool
- Name, used in the studio to find the tool
- Description, used to describe the tool

Configure your Function Tool
get_current_weather that declares the fields location (string)and unit (string):Field Details
Type
Use here any of the valid JSON types:object, string, integer, number, array, etc… The top-level type will most commonly be an object holding other properties.Learn more about all JSON types in the JSON Schema definition.Properties
Properties are definition of fields within an object. Here you can define any new variable. Nested properties are allowed.Required
Therequired array within an object defines which fields must be entered for a JSON payload to be validated.Publish your Tool
Creating a JSON Tool
Follow these steps to create a new JSON Schema ToolAdd a new Tool to a Project
+ button to add a new Entity to a Project.
Enter Tool Details
- Key, used by models to reference the tool
- Name, used in the studio to find the tool
- Description, used to describe the tool

Configure your JSON Schema Tool
get_current_weather that declares the fields location (string)and unit (string):Field Details
Type
Use here any of the valid JSON types:object, string, integer, number, array, etc… The top-level type will most commonly be an object holding other properties.Learn more about all JSON types in the JSON Schema definition.Properties
Properties are definition of fields within an object. Here you can define any new variable. Nested properties are allowed.Required
Therequired array within an object defines which fields must be entered for a JSON payload to be validated.Publish your Tool
Creating an HTTP Tool
Follow these steps to create a new HTTP Schema ToolAdd a new Tool to a Project
+ button to add a new Entity to a Project.
Enter Tool Details
- Key, used by models to reference the tool
- Name, used in the studio to find the tool
- Description, used to describe the tool

Configure your HTTP Tool

| Field | Description |
|---|---|
| URL | Enter the API URL as well as the HTTP Method for the call |
| Header | Define Request Header Key-value pairs |
| Payload | Define Request Body Payload Key-value pairs (these are translated to JSON at runtime) |
| Authentication | Define an optional Bearer Authentication field and Token (Tokens are encrypted when saved in Orq). |
{{variable}} syntax within any configuration field. The variable will be resolved at runtime when the payload is built for the HTTP call.Autogenerate Schema when using variables to ensure variable definition is correctly created.Publish your Tool
Creating an MCP Tool
Follow these steps to create a new MCP ToolAdd a new Tool to a Project
+ button to add a new Entity to a Project.
Enter Tool Details
- Key, used by models to reference the tool
- Name, used in the studio to find the tool
- Description, used to describe the tool
- MCP Server URL, a valid MCP url
- Authentication Type, an optional Bearer Authentication token, stored securely. When Bearer Token is selected, a Headers section becomes available to define additional key-value pairs sent with every request to the MCP server.

View your MCP configuration

Publish your Tool
Creating a Python Tool
Follow these steps to create a new Python ToolAdd a new Tool to a Project
+ button to add a new Entity to a Project.
Enter Tool Details
- Key, used by models to reference the tool
- Name, used in the studio to find the tool
- Description, used to describe the tool

Configure your Python Tool
name field defined and then further fetched using params.get('name').Ensure your return value is stored within the result field.
Publish your Tool
Versions
When you are done editing, click Publish to save your changes. You will be prompted to write a commit message and choose a version bump: major, minor, or patch.
- Patch (e.g.
v1.0.0tov1.0.1): small fixes, no behavior change - Minor (e.g.
v1.0.0tov1.1.0): new functionality, backwards compatible - Major (e.g.
v1.0.0tov2.0.0): breaking change or significant rework
v1.0.0, v1.1.0) and each entry shows the author and publish timestamp.
