Skip to main content
Glama
Sign In

DeriveAI x402 APIs

by io.github.deriveit33z-ship-it
OverviewDiscussionsAdmin

domain_infra

Domain infrastructure map. Full DNS records (A, AAAA, MX, NS, TXT, SOA, CAA), hosting provider, CDN detection, subdomain discovery via DNS brute-force and Certificate Transparency, IP geolocation.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to map (e.g., google.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description bears full responsibility. It mentions specific actions (DNS brute-force, Certificate Transparency subdomain discovery, IP geolocation) which imply network calls, but it does not disclose potential rate limits, response format, or that it is strictly read-only. It lacks explicit behavioral guarantees beyond listing its scope.

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 a single concise sentence that front-loads the core purpose ('Domain infrastructure map') followed by a dense, comma-separated list of features. No wasted words, every element adds value.

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?

Given the tool's complexity (various DNS records, subdomain discovery, geolocation) and lack of output schema, the description provides a thorough enumeration of what is returned. It does not mention prerequisites or limitations, but it covers the main behavioral aspects adequately for an initial invocation.

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?

The only parameter 'domain' is well-described in the schema with an example. The description does not add any additional syntax, constraints, or format details beyond what the schema provides. With 100% schema coverage, the baseline of 3 is 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 clearly states the tool's purpose: 'Domain infrastructure map' with a comprehensive list of DNS record types and additional features like hosting provider, CDN detection, subdomain discovery, and IP geolocation. It distinguishes from siblings like 'domain_enrich' by specifying the full scope of DNS records and subdomain discovery techniques.

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?

The description implies usage for comprehensive domain infrastructure mapping but does not explicitly compare to alternatives (e.g., 'domain_enrich') or state when not to use it. The agent can infer the tool's broad scope, but there is no explicit guidance on when to choose this over similar tools.

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

All DeriveAI x402 APIs 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