Skip to main content
Glama

NovaPixel LexGrid

domain_rdap_intel

Official RDAP query extracting domain registration date, domain age (<30 days anti-phishing alert), registrar, DNSSEC, ASN and EU/non-EU physical jurisdiction.

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": {
      "domain": "<domain>"
    },
    "name": "domain_rdap_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to query on RDAP (e.g. novapixel.it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully states what data is extracted and the under-30-day anti-phishing signal, but it does not describe failure behavior for unregistered domains, rate limits, authentication needs, or response structure.

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 a single dense sentence with no wasted wording. The query type is front-loaded and every listed field contributes useful scope information.

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 simple one-parameter read-only lookup, the description covers the main returned intelligence and a notable alert condition. It is nearly complete, though it could mention behavior for unregistered or unavailable domains since there is no output schema.

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 single domain parameter is fully documented in the schema, including an example, so the baseline is 3. The description adds only that the domain is fed to an RDAP query, without additional syntax, normalization, or validity constraints beyond the schema.

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?

States a specific verb and resource ("Official RDAP query") and enumerates the extracted intelligence fields, including registration date, registrar, DNSSEC, ASN, and jurisdiction. It is clearly a domain-registration lookup, though it does not explicitly distinguish itself from the sibling security-audit tools.

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?

Usage is implied through the anti-phishing alert for domains under 30 days old, suggesting security vetting. However, there is no explicit when-to-use versus when-not guidance, nor any named alternative for related domain intelligence needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources