Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

get_simulation_run_event

Read-only

Retrieve and analyze simulation event details from Paddle to verify delivery status, debug issues, and check payload and response data for troubleshooting.

Instructions

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

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.

If the destination URL is using a tunnel or proxy service, the response may be from the tunnel or proxy service, not the original server. Don't assume success or failure based on the status and response alone. Check the logs of the tunnel/proxy service and the destination 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 get.

Implementation Reference

  • The main handler function that implements the core logic for the 'get_simulation_run_event' tool. It destructures the required parameters (simulationId, simulationRunId, simulationEventId) and calls the Paddle SDK's simulationRunEvents.get method to retrieve the specific simulation run event.
    export const getSimulationRunEvent = async (
      paddle: Paddle,
      params: z.infer<typeof Parameters.getSimulationRunEventParameters>,
    ) => {
      try {
        const { simulationId, simulationRunId, simulationEventId } = params;
        const simulationRunEvent = await paddle.simulationRunEvents.get(simulationId, simulationRunId, simulationEventId);
        return simulationRunEvent;
      } catch (error) {
        return error;
      }
    };
  • Tool schema definition including method name, description prompt, Zod parameters schema reference, and required actions for the 'get_simulation_run_event' tool.
      method: "get_simulation_run_event",
      name: "Get an event for a simulation run",
      description: prompts.getSimulationRunEventPrompt,
      parameters: params.getSimulationRunEventParameters,
      actions: {
        simulationRunEvents: {
          read: true,
          get: true,
        },
      },
    },
  • src/api.ts:63-63 (registration)
    Registration of the handler function in the toolMap within PaddleAPI class, mapping the constant TOOL_METHODS.GET_SIMULATION_RUN_EVENT to funcs.getSimulationRunEvent.
    [TOOL_METHODS.GET_SIMULATION_RUN_EVENT]: funcs.getSimulationRunEvent,
  • src/constants.ts:55-55 (registration)
    Constant definition for the tool method name 'get_simulation_run_event' used in registration and tool definitions.
    GET_SIMULATION_RUN_EVENT: "get_simulation_run_event",
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=true, confirming it's a safe read operation. The description adds valuable behavioral context beyond annotations: it details the response structure (status, payload, request.body, response.body, response.statusCode) and warns about tunnel/proxy services affecting interpretation, which aids in debugging and understanding output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but could be more front-loaded. It starts with the purpose, then delves into detailed response fields and warnings. While informative, some sentences (e.g., about tunnel/proxy services) are lengthy and might bury key usage information, reducing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (retrieving specific events with debugging details), no output schema, and rich annotations, the description is fairly complete. It explains the response structure and caveats, though it lacks explicit error handling or prerequisites, which could enhance completeness for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with clear parameter descriptions in the input schema. The tool description does not add any parameter-specific information beyond what the schema provides, such as format examples or usage tips, so it meets the baseline without extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'retrieve an event sent by a simulation run from Paddle by its ID.' It specifies the verb ('retrieve'), resource ('event'), and source ('Paddle'), but does not explicitly differentiate it from sibling tools like 'list_simulation_run_events' or 'get_simulation_run', which might cause confusion in selection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools such as 'list_simulation_run_events' for multiple events or 'get_simulation_run' for run details, leaving the agent without context for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

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