Request
This endpoint expects an object.
Path of the Tool, including the name. This locates the Tool in the Humanloop filesystem and is used as as a unique identifier. For example: folder/name or just name.
Callable function specification of the Tool shown to the model for tool calling.
Additional fields to describe the Tool. Helpful to separate Tool versions from each other with details on how they were created or used.
Unique identifier for this Tool version. Each Tool can only have one version with a given name.
Description of the Version.
Response
Successful Response
Path of the Tool, including the name, which is used as a unique identifier.
Unique identifier for the Tool.
Name of the Tool, which is used as a unique identifier.
Unique identifier for the specific Tool Version. If no query params provided, the default deployed Tool Version is returned.
The number of logs that have been generated for this Tool Version
The number of logs that have been generated across all Tool Versions
Inputs associated to the Prompt. Inputs correspond to any of the variables used within the Tool template.
ID of the directory that the file is in on Humanloop.
Callable function specification of the Tool shown to the model for tool calling.
Additional fields to describe the Tool. Helpful to separate Tool versions from each other with details on how they were created or used.
Unique identifier for this Tool version. Each Tool can only have one version with a given name.
Description of the Version.
Long description of the file.
List of tags associated with the file.
The list of environments the Tool Version is deployed to.
The user who created the Tool.
Evaluators that have been attached to this Tool that are used for monitoring logs.
Aggregation of Evaluator results for the Tool Version.