Skip to main content
Glama
Sign In

TidyTools Free Web Data

by io.github.tidytools
OverviewDiscussionsAdmin

domain_whois

Read-only

Returns public RDAP registration details for one domain. Returns a limited free result and paid upgrade links. Apify Actor links can be paid with x402 via Apify, no Apify account needed. Send Authorization: Bearer tt_… for full results billed in TidyTools credits. Use for one domain. Not for batch work or unrestricted monitoring. Free: 3 per IP per UTC day; shared AI caller/ASN pool 50; 300 globally per day.

Input Schema

NameRequiredDescriptionDefault
urlNoWebsite URL alias for domain; supply one of domain or url.
domainNoOne public domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "domain"
+    ]
+  },
+  {
+    "required": [
+      "url"
+    ]
+  }
+]
    • addedInput schema / properties / url
      Added value: +{
+  "description": "Website URL alias for domain; supply one of domain or url.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "domain"
-]New value: +[]
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description discloses important behavior: limited free results, paid upgrade links, Authorization Bearer usage for full paid results, and detailed daily/IP/ASN quotas. This is unusually complete behavioral context for an agent.

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 description is front-loaded with purpose and then covers payment, auth, scope, and rate limits in a compact sequence. Some payment details are slightly dense and the repeated 'Returns... Returns...' phrasing could be tightened, but there is little wasted space.

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 read-only lookup tool with no output schema, it covers scope, access/auth, free-vs-paid behavior, and quotas well. It does not enumerate the registration fields returned, but RDAP registration details is a reasonably clear output expectation.

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 input schema already documents both domain and url with 100% description coverage. The description reinforces single-domain usage but does not add parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: returns public RDAP registration details for one domain. It also makes the single-domain scope explicit, but it does not explicitly differentiate this tool from close siblings such as domain_overview or domain_dns.

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?

It gives clear usage context: use for one domain, not for batch work or unrestricted monitoring. It does not name an alternative sibling tool for those excluded cases, so it falls short of full when-to-use/when-not/alternatives guidance.

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

All TidyTools Free Web Data toolsInspect
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.

Resources