domaindrift

Look up one domain

lookup_domain

Read-only

The latest signed observation of one domain: who runs its nameservers, mail, and CDN; certificate issuer and expiry; HTTPS reachability; per-record-type counts; and the Ed25519 receipt pointer. Keyless calls get this reduced preview, throttled to 1 request per 15 seconds per IP under a shared daily ceiling. Connect with a DomainDrift API key in an Authorization: Bearer header to get the complete signed record instead, metered against your account like any API request.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	Registrable domain name, e.g. "example.com"

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses key behavioral traits: throttling (1 req/15s per IP), shared daily ceiling for keyless calls, and authentication via API key for complete records. No contradictions.

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 concise (4 sentences), front-loaded with the main purpose, and every sentence adds necessary detail without redundancy.

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?

With no output schema, the description compensates by enumerating the returned data elements, explaining authentication options and rate limits, providing a complete picture for a single-parameter lookup tool.

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 schema already documents the 'domain' parameter with 100% coverage, and the description does not add parameter-specific semantics beyond contextualizing its usage. Baseline 3 is appropriate.

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 retrieves 'the latest signed observation of one domain' and lists specific data elements like nameservers, mail, CDN, certificate info, etc., distinguishing it from sibling tools that have different focuses.

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 explains when to use the tool (looking up a single domain's observation) and contrasts keyless vs authenticated access, but does not explicitly mention when not to use it or suggest alternatives among siblings.

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

All domaindrift tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: aggregate rollup, domain lookup, receipt verification, public keys, and daily digest. No overlap.

Naming Consistency3/5

Naming patterns are mixed: verb_noun (lookup_domain, resolve_receipt), noun_noun (internet_tape), gerund_noun (signing_keys), and a phrase (whats_changed_today). While readable, they lack a consistent convention.

Tool Count5/5

Five tools are well-suited for the domain intelligence service, covering essential operations without being excessive or insufficient.

Completeness4/5

The tool surface covers core functionality – aggregate stats, domain lookup, verification, and daily digest – but lacks batch queries or historical trends, which are minor gaps.

Resources

Need Help?