Skip to main content
Glama
Sign In

AIPayGen Site Intel

by io.github.Damien829
OverviewDiscussionsAdmin

Domain registration (RDAP/WHOIS)

domain_whois
Read-onlyIdempotent

Look up who registered a domain and when: registrar, creation and expiry dates, domain age, status codes, nameservers and DNSSEC, via RDAP (the modern WHOIS). Price: $0.002 per call.

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_whois"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name, e.g. openai.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds a genuinely useful operational fact not in the structured fields: a per-call price of $0.002, which lets an agent budget. It omits failure behavior — unregistered domains, TLDs without RDAP coverage — which would complete the picture.

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 sentence naming the resource and its outputs, followed by one short sentence on cost. No filler, no restatement of the tool name, and the core purpose is front-loaded before the price detail.

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?

No output schema exists, so the description's enumeration of returned fields carries the return-value burden well, and the RDAP parenthetical clarifies the underlying source. Missing edge-case behavior (no RDAP server for a TLD, unregistered domain) is a minor gap for a read-only lookup.

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?

Only one parameter, and the schema already documents it at 100% coverage with the same 'openai.com' example style. The description's mention of 'domain' adds no syntax, normalization, or format guidance beyond the schema, so the baseline 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?

States a specific verb and resource ('Look up who registered a domain') and enumerates exactly what comes back: registrar, dates, age, status codes, nameservers, DNSSEC. That is far more concrete than the title alone. It doesn't differentiate from close siblings like domain_report or dns_lookup, which is the only thing keeping it off a 5.

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 by the content list — an agent can infer this is the tool for registration metadata rather than DNS records. But there is no explicit when-to-use, when-not-to-use, or pointer to domain_report as the broader alternative, so the agent must compare sibling schemas itself.

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

All AIPayGen Site Intel 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