Skip to main content
Glama
Sign In
Qiniso

Qiniso

Official
by qinisolabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

validate_tld

Verify if a top-level domain (TLD) is real by checking against the authoritative IANA root-zone list. Avoid trusting fake TLDs like .zip or .crypto.

Instructions

USE THIS to check whether a top-level domain is real before trusting a domain or link — do NOT guess whether a TLD like .zip, .corp, .crypto or .web exists. Checks the suffix against the authoritative IANA root-zone list (kept current). Returns valid:false for TLDs that are not actually delegated.

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

Input Schema

NameRequiredDescriptionDefault
tldYesThe TLD to check, with or without a leading dot (e.g. 'zip' or '.zip').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Without annotations, the description discloses that checks are against the IANA root-zone list, kept current, and returns valid:false for non-delegated TLDs. It does not discuss idempotency or side effects, but for a validation tool, these are sufficiently transparent.

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 two sentences, front-loaded with 'USE THIS', and contains no extraneous words. Every part serves a purpose: examples, authoritative source, and expected return behavior.

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?

Given the tool has one parameter and no output schema, the description fully covers the input, process, and output. It explains what it validates, against which source, and what the result means, leaving no gaps.

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?

The tool description adds examples of TLDs to check but the parameter schema already fully describes the 'tld' parameter (with/without leading dot). Schema coverage is 100%, so the description provides marginal extra value beyond the 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 validates whether a top-level domain is real using the authoritative IANA root-zone list, providing specific examples like .zip and .corp. It distinguishes itself from siblings like validate_domain by focusing on TLDs alone.

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?

The description explicitly advises 'USE THIS to check whether a top-level domain is real before trusting a domain or link — do NOT guess' which provides strong when-to-use guidance. However, it does not mention alternatives or specific when-not-to-use scenarios, though siblings like validate_domain imply a different scope.

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