Skip to main content
Glama
Sign In
porkbun-mcp-server

porkbun-mcp-server

by Avicennasis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_invite

Generate a one-time account registration invite with optional pre-filled email and post-registration redirect URL. Invite expires in 48 hours.

Instructions

Create a one-time account registration invite. The invite expires in 48 hours. email pre-fills the registration form. return_url redirects the user after registration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
return_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/5.0
Behavior3/5

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

The description discloses key behaviors: the invite is one-time, expires in 48 hours, and the effects of email and return_url parameters. However, it does not mention return value, authentication requirements, or error conditions. With no annotations, this is partially complete.

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 three sentences, no wasted words. It front-loads the primary purpose and efficiently explains parameters and a behavioral trait.

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

Completeness3/5

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

For a tool with no output schema and no annotations, the description covers the main purpose and two parameters but omits return value format, prerequisites, and error handling. It is adequate but leaves gaps for an agent to fully understand the interaction.

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 description coverage is 0%, so the description must explain parameters. It does so effectively: '``email`` pre-fills the registration form' and '``return_url`` redirects the user after registration.' This adds functional meaning beyond the bare schema.

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: 'Create a one-time account registration invite.' This is a specific verb+resource combination that distinguishes it from siblings like get_invite_status and register_domain.

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 or when not to use this tool compared to alternatives. There is no mention of prerequisites, exclusions, or references to other tools.

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