Skip to main content
Glama
offsec-mcp

offsec-mcp

by nadirzhon

Whois

whois

Looks up domain registration data—registrar, registration dates, and nameservers—through RDAP for reconnaissance and domain ownership checks.

Instructions

Look up domain registration data (registrar, dates, nameservers) via RDAP.

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

Input Schema

NameRequiredDescriptionDefault
domainYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It helpfully discloses the protocol (RDAP), which implies read-only and gives a hint about data source/coverage, but says nothing about rate limits, TLD/registrar coverage gaps, or behavior for unregistered or non-RDAP domains.

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?

One tight sentence with the resource and expected output fields front-loaded; no wasted words.

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?

The tool is simple and an output schema exists, so return values needn't be explained. What's missing is minor but real: input format for the domain and failure behavior for unregistered/unsupported domains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% with no description of the single 'domain' parameter. The description does not clarify whether the input should be a bare apex domain, a subdomain, or a URL, which is a real ambiguity for lookup tools.

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 ('Look up') and resource ('domain registration data') with parenthetical examples of the fields returned (registrar, dates, nameservers). This is distinguishable from siblings like dns_lookup or recon_subdomains by resource type, though no sibling is explicitly named.

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 only implied: call it when you need registration/ownership data. There is no statement of when not to use it or how it relates to dns_lookup (which covers DNS records, a related but different need).

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