NicheDB

search_tlds

Read-onlyIdempotent

Top-level domains: every label in IANA's root, with type, registry, RDAP server and each registrar's one-year register/renew/transfer price (Porkbun, Dynadot, Cloudflare, OVHcloud). Sorted by renewal by default, because the first year is a promotion. best is the cheapest USD price across registrars; with registrar it is that registrar's own price in its currency. Answers carry facet counts. trap: true keeps only labels that renew at 2x the first year or more.

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": "search_tlds"
  }
}

Input Schema

Name	Required	Description
`q`	No	Text in the label, its Unicode form or the registry name (optional)
`idn`	No	true: internationalised labels only; false: ASCII only
`sort`	No	renew (default), register, transfer, restore, ratio, tld, registrars, type, manager, first_seen
`trap`	No	Only labels renewing at 2x the first year or more
`type`	No	generic, country-code, sponsored, generic-restricted, infrastructure, test; comma separated (optional)
`limit`	No	Rows to return, integer 1-500, default 50, e.g. 100
`order`	No	Sort direction: asc or desc, e.g. desc
`offset`	No	Rows to skip for paging, integer, default 0, e.g. 50
`status`	No	delegated (default), removed, or all, e.g. removed
`manager`	No	Exact registry name, as IANA writes it (optional)
`max_renew`	No	Highest renewal price (optional)
`registrar`	No	porkbun, dynadot, cloudflare, ovh (optional): only labels it sells, at its prices
`max_register`	No	Highest first-year price (optional)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 1, 2026

changedInput schema / properties / limit / description

Previous value: -"Default 50, max 500"New value: +"Rows to return, integer 1-500, default 50, e.g. 100"

changedInput schema / properties / offset / description

Previous value: -"Default 0"New value: +"Rows to skip for paging, integer, default 0, e.g. 50"

changedInput schema / properties / order / description

Previous value: -"asc or desc"New value: +"Sort direction: asc or desc, e.g. desc"

changedInput schema / properties / status / description

Previous value: -"delegated (default), removed, or all"New value: +"delegated (default), removed, or all, e.g. removed"

AddedSep 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description appropriately focuses on domain-specific behavior: default renewal sorting, the promotion rationale, `best` price semantics, facet counts, and the `trap` filter. It adds meaningful context beyond the annotations and schema, though it does not cover pagination or response shape in depth.

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 definition is dense but front-loaded: it establishes the dataset first, then defaults, then key field semantics, then the special `trap` filter. Every sentence carries useful information and there is no redundant restatement of schema details.

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 13-parameter tool with no output schema, the description covers the dataset, major return concepts (`best`, facet counts), default sorting, and filtering semantics. It could say more about the return shape or status/paging behavior, but it is substantially complete for correct invocation.

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. The description adds value by explaining why renewal is the default sort, how `best` behaves with and without `registrar`, and what `trap: true` retains, which goes beyond the schema's field-level descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly establishes the resource and dataset: every label in IANA's root, with type, registry, RDAP server, and registrar pricing. It is distinguishable from singular sibling `get_tld` and change-tracking `tld_changes`, though it never uses an explicit action verb like 'search' or 'list'.

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 explains intended use of specific filters (`trap`, `registrar`, default renewal sort), but it never says when to use this tool instead of siblings such as `get_tld` or `tld_changes`. Usage is implied through parameter semantics rather than explicit tool-selection guidance.

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

All NicheDB tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.