Chronulus MCP Server

Official

rescale_forecast

Rescale normalized forecast predictions (0 to 1) to a specific range using defined min and max values. Ideal when converting probabilities to custom units or adjusting forecasts for practical use cases.

Instructions

A tool that rescales the prediction data (values between 0 and 1) from the NormalizedForecaster agent to scale required for a use case

When to use this tool:

  • Use this tool when there is enough information from the user or use cases to determine a reasonable min and max for the forecast predictions
  • Do not attempt to rescale or denormalize the predictions on your own without using this tool.
  • Also, if the best min and max for the use case is 0 and 1, then no rescaling is needed since that is already the scale of the predictions.
  • If a user requests to convert from probabilities to a unit in levels, be sure to caveat your use of this tool by noting that probabilities do not always scale uniformly to levels. Rescaling can be used as a rough first-pass estimate. But for best results, it would be better to start a new Chronulus forecasting use case predicting in levels from the start.

How to use this tool:

  • To use this tool present prediction_id from the normalized prediction and the min and max as floats
  • If the user is also changing units, consider if the units will be inverted and set the inverse scale to True if needed.
  • When plotting the rescaled predictions, use a Rechart time series plot with the appropriate axes labeled and include the chronulus prediction explanation as a caption below the plot.
  • If you would like to add additional notes about the scaled series, put these below the original prediction explanation.

Input Schema

NameRequiredDescriptionDefault
invert_scaleNoSet this flag to true if the scale of the new units will run in the opposite direction from the inputs.
prediction_idYesThe prediction_id from a prediction result
y_maxYesThe expected largest value for the use case. E.g., for product sales, 0 would be the largest possible value would be given by the user or determined from this history of sales for the product in question or a similar product.
y_minYesThe expected smallest value for the use case. E.g., for product sales, 0 would be the least possible value for sales.

Input Schema (JSON Schema)

{ "properties": { "invert_scale": { "default": false, "description": "Set this flag to true if the scale of the new units will run in the opposite direction from the inputs.", "title": "Invert Scale", "type": "boolean" }, "prediction_id": { "description": "The prediction_id from a prediction result", "title": "Prediction Id", "type": "string" }, "y_max": { "description": "The expected largest value for the use case. E.g., for product sales, 0 would be the largest possible value would be given by the user or determined from this history of sales for the product in question or a similar product.", "title": "Y Max", "type": "number" }, "y_min": { "description": "The expected smallest value for the use case. E.g., for product sales, 0 would be the least possible value for sales.", "title": "Y Min", "type": "number" } }, "required": [ "prediction_id", "y_min", "y_max" ], "title": "rescale_forecastArguments", "type": "object" }
ID: idtstx1trt