Skip to main content
Glama
Sign In

VerifyLite

by io.github.SecondShotAI
OverviewDiscussionsAdmin

Domain registration, DNS, and email security

domain_report
Read-only

Domain intelligence: WHOIS/RDAP registration (registrar, created and expiry dates, status, name servers) plus DNS records (A, AAAA, MX, NS, TXT, CAA) and email security (SPF, DMARC), with flags for new, expiring or misconfigured domains, as one JSON object. Useful for vetting a company, vendor or link before trusting it. Not charged for invalid or reserved domain names. Paid via x402; see list_prices.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name (example.com) or a URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds valuable behavioral context: results are one JSON object, include flags for new/expiring/misconfigured domains, invalid/reserved domains are free, and paid access is via x402 with list_prices.

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 front-loaded with the tool's scope, followed by the use case and billing caveats. Every sentence contributes useful information 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?

For a complex domain-intelligence tool with a single parameter and no output schema, the description adequately explains the data sources, return shape, flags, and billing constraints. No essential invocation detail is missing.

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?

There is only one parameter and schema coverage is 100%, so the schema already fully documents it as a domain name or URL. The description does not add format or parsing details beyond what the schema provides, making the baseline 3 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 names a specific resource and enumerates exactly what is returned: WHOIS/RDAP registration, DNS records, and email security data. An agent can distinguish it from sibling tools such as check_site_safety or name_lookup by the domain-registration and DNS focus.

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 use case ('vetting a company, vendor or link before trusting it') and notes billing behavior for invalid/reserved domains. It does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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

All VerifyLite 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