Dodo Payments Agent Plugin
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DODO_PAYMENTS_API_KEY | Yes | Dodo Payments API key (dodo_test_... or dodo_live_...) | |
| DODO_PAYMENTS_ENVIRONMENT | No | API environment |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| executeA | Runs JavaScript code to interact with the Dodo Payments API. You are a skilled TypeScript programmer writing code to interface with the service. Define an async function named "run" that takes a single parameter of an initialized SDK client and it will be run. For example: You will be returned anything that your function returns, plus the results of any console.log statements. Do not add try-catch blocks for single API calls. The tool will handle errors for you. Do not add comments unless necessary for generating better code. Code will run in a container, and cannot interact with the network outside of the given SDK client. Variables will not persist between calls, so make sure to return or log any data you might need later. Remember that you are writing TypeScript code, so you need to be careful with your types. Always type dynamic key-value stores explicitly as Record<string, YourValueType> instead of {}. |
| search_docsA | Search SDK documentation to find methods, parameters, and usage examples for interacting with the API. Use this before writing code when you need to discover the right approach. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: execute runs JavaScript to interact with the API, while search_docs retrieves documentation. There is no ambiguity between them.
Both tool names use a verb-based pattern: 'execute' and 'search_docs'. This is consistent and clear, following a simple imperative style.
With only 2 tools, the set is minimal but well-scoped for its design: a single execute tool covers all API operations via code, and search_docs provides necessary documentation. This unconventional approach earns a slightly reduced score but is still reasonable.
The execute tool can perform any CRUD operation on the Dodo Payments API through TypeScript code, providing full coverage of the domain. The search_docs tool ensures agents can discover the correct methods. No obvious gaps exist.