$0.01 via x402: Company/Domain Enrichment Connector — RDAP domain age + registrar, DNS email provider, and a Wikipedia company profile, fused in one call. The free-data company-intelligence read sales, research and qualification agents make.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Company domain, e.g. stripe.com | |
| x_payment | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist. The description mentions 'read' and 'free-data' but also '$0.01 via x402', creating confusion about cost and idempotency. No behavioral details like side effects or auth requirements are provided.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with key info in the first. The second sentence is slightly awkward but still efficient. Minor punctuation issues do not detract significantly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description fails to explain return format, error handling, or usage of 'x_payment'. Significant gaps remain for agent selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50% with only 'domain' described. The description adds no detail about 'x_payment' and does not clarify parameter formatting or constraints beyond the schema's minimal info.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it enriches company/domain data with RDAP, DNS, and Wikipedia data, distinguishing it from related tools like b2b_lead_enrichment or wikipedia_lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use for sales, research, and qualification agents but lacks explicit when-to-use or when-not-to-use guidance, and does not mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.