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

porkbun-mcp-server

by Avicennasis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_glue

Retrieve glue records (host A/AAAA records) registered for a domain. Returns an empty list if none exist.

Instructions

List glue records (host A/AAAA records at the registrar) for domain. Returns an empty list if no glue records exist.

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": {
      "domain": "<domain>"
    },
    "name": "get_glue"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description discloses one behavioral trait: 'Returns an empty list if no glue records exist.' It implies a read-only operation (listing), but does not explicitly state idempotency, authentication needs, or potential errors for invalid domains.

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?

Two concise sentences: the first defines the core function with helpful clarification, the second covers the edge case of no results. No unnecessary words.

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?

Despite lacking an output schema, the description mentions return type ('list') and edge case ('empty list'). However, it does not describe the structure of each glue record (e.g., hostname, IP fields), which would help the agent interpret results fully.

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

Parameters2/5

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

Schema coverage is 0% and the description only mentions the domain parameter via a template placeholder (``domain``). It does not explain valid formats, constraints, or what happens if the domain does not exist or is not registered, leaving the agent with limited guidance.

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 verb 'List' and resource 'glue records' for a specific domain, with an explanatory parenthetical about host A/AAAA records at the registrar. It distinguishes from sibling tools (create_glue, delete_glue, update_glue) by indicating this is the read-only list operation.

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

Usage Guidelines3/5

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

The description implicitly tells the agent to use this tool when needing to view glue records for a domain, but does not provide explicit when-to-use or when-not-to-use guidance relative to alternatives like get_dns_record or list_dns_records.

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