Dodo Payments MCP

execute

Destructive

Run JavaScript against the Dodo Payments API with an SDK client for the signed-in business, in the mode of the session (test or live). Needs sign-in: without it the call returns 401 and the client starts sign-in.

Call search first to find the SDK method and its parameters. Define async function run(client) { ... }. The tool returns the value of run and the console.log output. Each call runs in a fresh sandbox with no network except the API: return everything you need. Do not wrap single calls in try/catch. Write calls change real data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "execute"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	Code to execute.
`intent`	No	Task you are trying to perform. Used for improving the service.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that each call runs in a fresh sandbox with no network except the API, that the tool returns the run value and console.log output, and that the client triggers sign-in when unauthenticated. It also reinforces that write calls change real data, which aligns with destructiveHint=true and adds practical execution context.

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

Conciseness5/5

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

The description is compact and front-loaded with the core operation, followed by the required search-first workflow, execution contract, and important caveats. Each sentence contributes concrete operational value without redundancy.

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

Completeness5/5

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

For an execution tool with no output schema, the description covers authentication behavior, environment mode, sandbox constraints, return value semantics, and write-side effects. An agent has enough information to invoke it correctly and understand the main risks.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents both parameters. The description adds useful meaning to the code parameter by specifying the required async function run(client) shape and the expectation to return everything needed, though it does not explain the intent parameter beyond what the schema provides.

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

Purpose5/5

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

The description states a specific verb and resource: run JavaScript against the Dodo Payments API using an SDK client for the signed-in business, in the session's test or live mode. It clearly distinguishes this execution environment from the companion search tool by directing the agent to use search first to locate SDK methods.

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

Usage Guidelines4/5

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

It gives clear procedural guidance: call search first to find the SDK method and parameters, define an async function run(client), and avoid wrapping single calls in try/catch. It also states the sign-in prerequisite and the 401 behavior. It does not explicitly describe when not to use this tool versus alternatives, so it falls short of a 5.

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

All Dodo Payments MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?