Skip to main content
Glama
oborseth

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Configure Auto Topup

configure_auto_topup
DestructiveIdempotent

Set the top-up amount and turn threshold-based automatic balance top-ups on or off to prevent orders failing from insufficient funds.

Instructions

Set the top-up amount, and/or turn auto top-up on or off.

amount_cents (integer US cents) is what a top-up adds, and it stands on its own: top_up_account_credit charges this same figure on demand, so setting it without enabling automation is a normal thing to do. Capped at $500 (50000) with a $5 floor when set through the API; a larger figure has to be set by the account holder at https://porkbun.com/account/api and is honoured as-is.

enabled: true (with threshold_cents) additionally makes it fire by itself: an order that drops the balance below threshold_cents charges the saved payment method for the amount and adds it — the way to stop an unattended workflow dead-ending on INSUFFICIENT_FUNDS. enabled: false stops it firing on a threshold but KEEPS the amount on file.

Confirm the numbers with the user before calling: this authorises charges to their card. No card is added or changed here, and none can be added over the API. Supports dry_run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoDeprecated alias of `amount_cents`, same unit (integer US cents). Send `amount_cents` instead.
dry_runNoIf true, validate only — returns wouldSucceed and changes nothing.
enabledNoTrue to switch auto top-up on (threshold required, plus an amount either here or already on file), false to switch it off. Omit it to change only the amount.
thresholdNoDeprecated alias of `threshold_cents`, same unit (integer US cents). Send `threshold_cents` instead.
amount_centsNoWhat a top-up adds, 500-50000 when set via the API. Can be sent on its own. E.g. 10000 = $100. Integer US cents: 803 means $8.03, not $803.
threshold_centsNoBalance below which a top-up fires. Required when enabling. E.g. 2000 = $20. Integer US cents: 803 means $8.03, not $803.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.39.4

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark this destructive/non-read-only/idempotent, and the description adds context the annotations cannot: it authorises real card charges, requires user confirmation, neither adds nor changes cards (nor can a card be added over the API), and that disabling keeps the amount on file. This is exactly the behavioral detail that goes beyond structured hints.

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

Conciseness4/5

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

Front-loaded with the core action, then structured into per-parameter paragraphs using backticked names. It is on the long side and repeats some cent-unit examples that also appear in the schema, but each paragraph carries usable information rather than filler.

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?

With no output schema, the description still discloses the dry_run return (`wouldSucceed`) and what changes vs. persists for each flag combination, covering the interaction model an agent needs for a 6-parameter opt-in/opt-out mutation tool.

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 baseline is 3, but the description genuinely adds meaning beyond it: `amount_cents` stands on its own and can be set without enabling, the $500 cap/$5 floor behave differently via API vs. account settings, and `enabled: false` preserves the stored amount — none of which the schema states.

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 first sentence states a precise verb+resource: setting the top-up amount and/or toggling auto top-up. The body further distinguishes this from `top_up_account_credit` (on-demand charge of the same figure) and from reading state via `get_auto_topup`, so an agent can place it among its siblings without opening a schema.

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?

It explicitly covers the when-to-use conditions: setting `amount_cents` alone is normal, `enabled: true` with a threshold makes it fire, `enabled: false` stops firing but keeps the amount, and dry_run validates. It also names the alternative tool (`top_up_account_credit`) and gives an instruction to confirm with the user before calling.

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

Deploy Server

Other Tools