DeriveAI x402 APIs

domain_enrich

Domain enrichment: returns company name, description, detected tech stack (React, WordPress, Shopify, etc.), social media links (Twitter, LinkedIn, GitHub), email addresses, and redirect info for any domain.

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

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain name to enrich (e.g., google.com, aramco.com)

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 19, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavior. It lists output fields but does not mention potential limitations (e.g., whether the domain must be publicly accessible, rate limits, or whether it performs a live scan or uses cached data). This is a significant gap for a tool that fetches external data.

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?

The description is a single concise sentence that lists the rich set of data returned. It front-loads the purpose and is efficient, though it could be slightly longer to include usage nuance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (multiple data types returned) and no annotations, the description covers output types but misses behavioral aspects like data freshness, dependency on third-party sources, and potential errors. It is adequate for basic understanding but incomplete for nuanced usage.

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?

Schema coverage is 100% for the single parameter 'domain', which has a clear description. The description reinforces the parameter by giving examples (e.g., google.com, aramco.com) and connecting it to the enrichment output, but adds no new semantics beyond what the schema already provides.

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?

The description clearly states that the tool enriches a domain with company info, tech stack, social links, emails, and redirect info. It is specific about the resource (domain) and the type of data returned, but doesn't explicitly distinguish it from siblings like domain_infra or site_audit, which might also relate to domains.

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 enriching a domain with business information, but does not explicitly state when to use this tool versus domain_infra or site_audit. It lacks guidance on alternatives or when not to use it.

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 tools Inspect

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.