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

porkbun-mcp-server

by Avicennasis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_pricing_for_tld

Get pricing for a single TLD (e.g., .com) from Porkbun's cached pricing table. Optionally force refresh to bypass the cache.

Instructions

Pricing for a single TLD (e.g. 'com'). Derived from the same cached pricing table as get_pricing — no separate API call. force_refresh=True bypasses the cache.

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": {
      "tld": "<tld>"
    },
    "name": "get_pricing_for_tld"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldYes
force_refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.2/5.0
Behavior4/5

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

Discloses caching behavior, that no separate API call is made, and force_refresh bypasses cache. No annotations provided, so description carries full burden; these details add transparency.

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 sentences, front-loaded with purpose, no wasted words. Efficient and clear.

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?

For a simple 2-param tool with no output schema, description covers purpose, relationship to sibling, caching, and parameter hint. Lacks return value details but adequate for complexity.

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?

Description mentions force_refresh effect but doesn't document tld parameter explicitly beyond example. Schema coverage is 0%, but description adds some value for force_refresh. Overall moderate improvement over schema alone.

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?

Clearly states it gets pricing for a single TLD, with example 'com'. Distinguishes from sibling get_pricing by noting it's derived from the same cached table with no separate API call.

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?

Implies usage for single TLD vs. get_pricing for broader scope. Mentions force_refresh to bypass cache. Could be more explicit about when not to use, but provides context.

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