Skip to main content
Glama
dodopayments

Dodo Payments Agent Plugin

Official
by dodopayments
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

Server Quality Checklist

83%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v0.4.0

  • Disambiguation5/5

    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.

    Naming Consistency5/5

    Both tool names use a verb-based pattern: 'execute' and 'search_docs'. This is consistent and clear, following a simple imperative style.

    Tool Count4/5

    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.

    Completeness5/5

    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.

  • Average 4.6/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • 4 of 4 community issues answered or closed in the last 6 months
    • 5 commits in the last 12 weeks
    • Last stable release on
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI is passing

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • This repository includes a glama.json configuration file.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • View related servers

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior4/5

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

    The description does not contradict the readOnlyHint=true annotation. It adds context by stating the tool is for discovery and should be used before coding, which implies no side effects. No mention of rate limits or pagination, but the annotation already covers safety.

    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 concise: two sentences that clearly state the purpose and when to use it. No unnecessary words.

    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?

    With no output schema, the description conveys the tool's function and intended use adequately. It could mention the output format briefly, but the description is sufficient for a read-only search tool.

    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?

    All three parameters are described in the input schema (100% coverage). The description does not provide additional detail beyond the schema, such as search syntax or result formatting. Baseline 3 is appropriate.

    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 clearly states the tool's purpose: 'Search SDK documentation to find methods, parameters, and usage examples.' It uses a specific verb ('Search') and resource ('SDK documentation'), and distinguishes from the sibling 'execute' tool.

    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?

    The description provides explicit usage guidance: 'Use this before writing code when you need to discover the right approach.' It does not mention alternatives or when not to use, but given only one sibling, it is adequate.

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

  • Behavior5/5

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

    With no annotations, the description fully discloses behavior: returns function return and console.log, handles errors, runs in container, no network outside SDK, and variable non-persistence.

    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 appropriately sized for a complex tool, front-loaded with purpose, then example, then clear bullet points. Every sentence adds value.

    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?

    Despite no output schema, the description explains return values (function return and console.log). It covers all necessary context for a complex code execution tool, including environment constraints.

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

    Parameters5/5

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

    Even with 100% schema coverage, the description enriches parameter semantics with code structure requirements (async function named 'run'), typing advice, and example usage, going beyond the simple schema descriptions.

    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 clearly states 'Runs JavaScript code to interact with the Dodo Payments API,' providing a specific verb and resource. It includes an example and distinguishes from the sibling tool 'search_docs'.

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

    Usage Guidelines5/5

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

    The description provides detailed usage guidelines: 'Do not add try-catch blocks...', 'Variables will not persist between calls,' and 'Cannot interact with network outside...', explicitly guiding when and how to use the tool.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

dodo-agent-plugin MCP server

Copy to your README.md:

Score Badge

dodo-agent-plugin MCP server

Copy to your README.md:

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/dodopayments/dodo-agent-plugin'

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