Skip to main content
Glama

LexGrid — NetSec, Deliverability & RDAP

domain_rdap_intel

Read-onlyIdempotent

[Official RDAP registry query. Read-only, non-destructive, side-effect free]. Queries official ICANN and regional TLD RDAP endpoints to extract domain registration age (<30 days anti-phishing alert), registrar identity, DNSSEC cryptographic signing status, Autonomous System Number (ASN), and EU vs non-EU legal jurisdiction. Usage: Use this tool to verify domain provenance, registrar identity, and anti-phishing domain age. Returns: JSON object with { domain: string, registrationDate: string, domainAgeDays: number, isNewlyRegistered: boolean, registrar: string, dnssec: boolean, asn: number | null, jurisdiction: 'EU' | 'NON_EU', riskFlags: string[] }.

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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with non-destructive/side-effect-free language. It adds useful behavior beyond annotations by naming the official RDAP data sources, the extracted fields, and the <30-day anti-phishing alert, though it omits rate limits, error behavior, and authentication needs.

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 the core purpose and then separated into Usage and Returns sections. It is mostly efficient, though the read-only/non-destructive/side-effect-free line partly repeats what the annotations already state.

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 lookup, the definition covers the purpose, usage context, and return fields, and annotations cover the safety profile. It lacks explicit failure or rate-limit behavior, but it is otherwise complete enough for an agent to invoke it correctly.

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?

Schema coverage is 100% and the single parameter already includes a description and example. The description does not add syntax, format, or constraint details for the domain parameter beyond what the schema provides, so the baseline score of 3 applies.

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: it queries official ICANN and regional TLD RDAP endpoints to extract registration age, registrar, DNSSEC, ASN, and jurisdiction. The purpose is clear and distinct from a TLS/HTTP inspector or email deliverability audit, but it does not explicitly name or differentiate itself from the sibling tools.

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 a clear usage sentence: use it to verify domain provenance, registrar identity, and anti-phishing domain age. It does not mention when not to use it or compare it against the sibling tools, so it stops short of explicit routing guidance.

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