Skip to main content
Glama

YRUZ Domain Intel (0.01 USDC)

domain_intel
Read-onlyIdempotent

Domain intelligence in one call: DNS records (A, AAAA, MX, NS, TXT, CAA, SOA), email security (SPF with lookup count, DMARC policy, MTA-STS, TLS-RPT, BIMI, DKIM on common selectors), registration from RDAP (registrar, created, expires, status, DNSSEC) and the TLS certificate (issuer, expiry). Scored 0-100 with every issue and its fix. Ideal for vetting a vendor, a sender or a lead. Price: 0.01 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"domain_intel"}. Same tool over HTTP: https://yruz.one/api/domain?domain=yruz.one

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

Input Schema

NameRequiredDescriptionDefault
domainYesdomain name (required), e.g. example.com; a URL or email works too

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / domain / examples
      Added value: +[
      +  "yruz.one"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the bar is low, yet the description adds real operational detail: price (0.01 USDC), x402 payment on Base or Solana with no account or API key, invalid input refused before payment, failed runs never charged, and a PaymentRequired response otherwise. That is exactly the pre-call behavior an agent 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?

Capabilities are front-loaded and most sentences carry payload (outputs, price, payment failure modes, example-call pointer). Minor waste in the trailing HTTP endpoint line, which does not help an MCP agent decide or invoke.

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?

No output schema exists, and the description compensates by enumerating the returned sections (DNS, SPF/DMARC/MTA-STS/BIMI/DKIM, RDAP, TLS cert) plus the 0-100 score and per-issue fixes. For a one-parameter tool with full schema coverage, nothing needed to call it correctly 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?

Only one parameter and schema coverage is 100% – the schema already documents 'domain' including that a URL or email is accepted. The description adds no additional syntax, normalization or format guidance beyond what the schema provides, so it sits at the baseline.

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?

Opens with a specific verb+resource ('Domain intelligence in one call') and enumerates exactly what is returned: DNS record types, email security checks, RDAP registration fields and TLS certificate data. The scope is unmistakable, but adjacent siblings such as url_safety_check or site_audit are never named, so an agent must infer the boundary itself.

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?

'Ideal for vetting a vendor, a sender or a lead' gives concrete use cases, and the payment note explains what happens without payment (x402 PaymentRequired returned). It stops short of stating when NOT to use it or which sibling to prefer for narrower checks.

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.