tld.expert

Get TLD prices

get_tld_prices

Read-onlyIdempotent

Use this when the user asks what a domain extension costs, where it is cheapest, or what it renews at. Returns dated first-year, renewal and transfer prices per registrar (Porkbun, Dynadot, Cloudflare, Namecheap where tracked), the cheapest direct buy, the wholesale floor, and a renewal-trap flag when the renewal is 2x+ the intro price. Prices are the TLD standard price, not premium names. Also answers "what does it cost over 5 years": true_cost gives each registrar's 1/3/5/10-year cost, the cheapest path per horizon (stay, or register at one and transfer after year one for gTLDs) and recent renewal price changes, each with source URL and checked date.

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": {
      "tlds": "<tlds>"
    },
    "name": "get_tld_prices"
  }
}

Input Schema

Name	Required	Description	Default
`tlds`	Yes	TLDs to price, e.g. ["com", "ai", "io"]. Max 20.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds real behavioral context beyond that: the data is dated with source URLs and checked dates, registrar coverage is bounded ('where tracked'), and the renewal-trap rule (2x+ intro) is disclosed. No rate limits or latency expectations are given, keeping it below a 5.

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?

The use-case trigger is front-loaded, followed by return contents and then the true_cost extension. Every clause carries information, but the second half is a long run-on covering multiple return subtopics, which slightly dilutes scanability.

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?

There is no output schema, so the description must carry the return-value burden, and it does: it names the price types, the registrars, the cheapest-buy and wholesale fields, the trap flag, and the true_cost horizons with provenance metadata. An agent can decide to call this and set expectations without opening anything else.

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?

Schema coverage is 100% and the single tlds parameter is fully described in the schema, including dot-optional format and the max of 20. The description says prices are returned per TLD but adds no new syntax or format guidance, so the baseline 3 applies.

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?

Names a specific verb and resource (TLD prices) and enumerates exactly what is returned: first-year, renewal, transfer prices per registrar, cheapest direct buy, wholesale floor, renewal-trap flag, plus true_cost horizons. This is clearly distinguishable from siblings like explain_tld or check_domain_availability, which would not return pricing tables.

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?

Gives explicit trigger conditions ('what a domain extension costs, where it is cheapest, or what it renews at') and a scope exclusion ('TLD standard price, not premium names'), which prevents misuse. It does not name sibling tools or tell the agent to route premium-name queries elsewhere, so it stops short of full alternative routing.

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

All tld.expert tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?