Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

domain_rdap_ip

Read-only

Fetch the RDAP allocation record for one public IP address. Provide an address from a DNS A or AAAA answer. Returns network, organization, CIDRs, allocation country, and registry-provided origin ASNs; country is not 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": {
      "ip": "<ip>"
    },
    "name": "domain_rdap_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesOne public IPv4 or IPv6 address; private and reserved addresses are rejected.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower. The description still adds real value by listing what comes back (network, organization, CIDRs, allocation country, origin ASNs) and by explicitly warning that country is not geolocation, a genuinely useful caveat an agent would otherwise misread.

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?

Three short sentences, front-loaded with the action and scope, then input guidance, then return contents and the geolocation caveat. No filler, every clause earns its place.

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?

An output schema exists, so return shape needn't be spelled out, and the description still summarizes the key fields and one important misinterpretation risk. For a single-parameter read-only lookup this is close to complete, with only the missing cross-reference to sibling tools as a gap.

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% and the single 'ip' parameter is already documented with the public/private rejection rule. The description echoes the public-address constraint and adds a mild note about sourcing it from DNS, but contributes little beyond the schema.

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 verb and resource: 'Fetch the RDAP allocation record for one public IP address.' The IP-address scope implicitly separates it from domain_rdap_domain, though that sibling is never named, so the differentiation is inferred rather than explicit.

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?

'Provide an address from a DNS A or AAAA answer' gives some context on where the input should come from, which implies a lookup-after-resolution workflow. However, it never says when to use this versus domain_dns_resolve or domain_rdap_domain, and offers no exclusions.

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

All Crawlora MCP 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