toolvend - utility APIs for agents

rdap

Domain registration data (modern WHOIS) via RDAP: registrar, created/expiry dates, status, nameservers, DNSSEC. Paid per call: $0.005 in USDC via x402.

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": "rdap"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain to look up (path parameter)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedAug 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the burden, and it discloses the most consequential behavioral trait: this is a paid call at $0.005 USDC per invocation via x402. That pricing/auth signal is exactly the kind of context structured fields don't provide. It stops short of describing failure behavior (e.g., NXDOMAIN, unregistered domains) or response shape.

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?

Two compact sentences, zero filler. The core identity and returned data are front-loaded, and the pricing caveat is appended as a secondary but essential note.

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?

A read-only single-parameter lookup with a partial return-field listing and the critical payment cost disclosed — enough for an agent to invoke it correctly. The absence of an output schema means a fuller account of the response envelope (and error cases) would have helped, keeping it just below top marks.

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 description coverage is 100% for the single 'domain' parameter, so the schema already explains its meaning and role as a path parameter. The description adds nothing beyond that about the parameter. Baseline 3 applies.

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?

States a specific resource and retrieval mode: 'Domain registration data (modern WHOIS) via RDAP', then enumerates the returned fields (registrar, dates, status, nameservers, DNSSEC). It's clear what the tool does, though it never explicitly distinguishes itself from the 'dns' sibling, which overlaps on nameservers/DNSSEC.

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?

Usage is only implied by the field list — an agent can infer this is the tool for registrar/expiry/status data rather than raw DNS records. There is no explicit when-to-use guidance, no mention of when to prefer 'dns' or 'url-inspect' instead, and no note on unregistered or malformed domains.

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

All toolvend - utility APIs for agents 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.

Resources

Need Help?