Skip to main content
Glama
PaddleHQ
by PaddleHQ

replay_simulation_run_event

Resend a specific event from a Paddle simulation run using its ID to retest individual event delivery without creating a new simulation run.

Instructions

This tool will resend an event sent by a simulation run from Paddle using its ID.

This is useful to retest the sending of an individual event within a simulation run rather than creating a new simulation run and sending all events again.

Paddle creates a new simulation run event entity for the replay, related to the same simulation run.

If successful, the response includes the new simulation run event entity.

Check the following details to understand the success or failure of the event according to Paddle and debug issues:

  • status: Status of the event according to Paddle.

    • pending: No attempt has been made to deliver the event yet.

    • success: The event was delivered successfully.

    • failure: Paddle tried to deliver the simulated event, but it failed. If response object is null, no response received from the server. Check the notification setting endpoint configuration.

    • aborted: Paddle couldn't attempt delivery of the simulated event.

  • payload: Payload sent by Paddle for this event within the simulation.

  • request.body: Request body sent by Paddle.

  • response.body: Response body sent by the responding server. May be empty for success responses.

  • response.statusCode: HTTP status code sent by the responding server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
simulationIdYesPaddle ID of the simulation entity associated with the run the event was sent as part of.
simulationRunIdYesPaddle ID of the simulation run entity the event was sent as part of.
simulationEventIdYesPaddle ID of the simulation event entity to replay.

Implementation Reference

  • The handler function that executes the replay_simulation_run_event tool. It destructures simulationId, simulationRunId, and simulationEventId from params and calls paddle.simulationRunEvents.replay() with them, returning the result or error.
    export const replaySimulationRunEvent = async ( paddle: Paddle, params: z.infer<typeof Parameters.replaySimulationRunEventParameters>, ) => { try { const { simulationId, simulationRunId, simulationEventId } = params; const simulationRunEvent = await paddle.simulationRunEvents.replay( simulationId, simulationRunId, simulationEventId, ); return simulationRunEvent; } catch (error) { return error; } };
  • src/tools.ts:914-924 (registration)
    The tool registration in the tools array, defining the method name, name, description (from prompts), parameters schema (from params), and required actions (write and replay on simulationRunEvents).
    method: "replay_simulation_run_event", name: "Replay an event for a simulation run", description: prompts.replaySimulationRunEventPrompt, parameters: params.replaySimulationRunEventParameters, actions: { simulationRunEvents: { write: true, replay: true, }, }, },
  • src/api.ts:64-64 (registration)
    Maps the TOOL_METHODS.REPLAY_SIMULATION_RUN_EVENT constant to the replaySimulationRunEvent handler function in the toolMap used by PaddleAPI to dispatch tool calls.
    [TOOL_METHODS.REPLAY_SIMULATION_RUN_EVENT]: funcs.replaySimulationRunEvent,
  • Constant defining the tool method string 'replay_simulation_run_event' used in TOOL_METHODS for registration and mapping.
    REPLAY_SIMULATION_RUN_EVENT: "replay_simulation_run_event",

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaddleHQ/paddle-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server