Skip to main content
Glama

BRAINIAC Public Infrastructure Lookups

IANA RDAP bootstrap lookup

public-infrastructure_iana-tld-rdap-bootstrap
Read-onlyIdempotent

Return IANA RDAP base URLs for a domain, IP or ASN from the vendored bootstrap registries. Price $0.01 USDC. POST /api/v1/public-infrastructure/iana-tld-rdap-bootstrap. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "public-infrastructure_iana-tld-rdap-bootstrap"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNoip, string, length 3 to 64. Optional.
asnNoasn, value. Optional.
fullNofull, string, one of dns, ipv4, ipv6, asn. Optional.
domainNodomain, string, length 1 to 253. Optional.

Output Schema

NameRequiredDescriptionDefault
typeNotype. String.
entryNoentry. Object.
queryNoquery. String.
sourcesNosources. Array.
limitationsNolimitations. Array.
publicationNopublication. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the read-only/idempotent annotations, it discloses the price ($0.01 USDC) and, importantly, that an unpaid call returns x402 payment terms without executing — a behavioral trait an agent cannot infer from the annotations. It stops short of describing latency, caching, or how the 'full' registry selector changes results.

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?

Three short sentences, front-loaded with the purpose, then endpoint and payment terms. Nothing is padded, though the raw POST path is arguably redundant with the tool's own name.

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?

With an output schema, rich annotations, and fully documented parameters, the description only needs to cover purpose and payment gating, which it does. The remaining gap is the ambiguity of four all-optional parameters and the 'full' selector, which is left entirely to the schema.

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%, so the baseline is 3. The description adds only high-level meaning ('for a domain, IP or ASN'), and notably never explains the 'full' enum that selects which bootstrap registry (dns/ipv4/ipv6/asn) is returned, nor how optional parameters interact.

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?

Names a specific verb and resource: 'Return IANA RDAP base URLs ... from the vendored bootstrap registries', with the accepted input kinds (domain, IP, ASN) stated up front. An agent can tell this is a read-only registry lookup rather than a general IP-to-ASN resolver, though it does not explicitly contrast itself with siblings.

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 implied by the input kinds (use it when you need RDAP base URLs for a domain/IP/ASN), but there is no explicit when-to-use/when-not framing or named alternative. The description never says what to do when several of the four optional parameters are supplied at once.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources