Skip to main content
Glama

Rdap

by io.github.pipeworx-io

Asn

asn
Read-onlyIdempotent

ASN allocation record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "number": 15169
+  },
+  {
+    "number": 3356
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "RDAP ASN allocation record",
+  "type": "object"
+}
  2. First observed

TDQS

D1.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the behavioral profile. The description adds no value beyond these annotations, missing context such as data source or response nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, but it lacks substantive content. Every sentence should earn its place; the single phrase does not convey enough information for effective tool use.

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

Completeness2/5

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

Despite having an output schema, the description fails to provide context about the tool's scope, return type, or how the parameter relates to the resource. It is insufficient for a one-parameter tool with sibling alternatives.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and no parameter explanation in the description, the single required parameter 'number' is left unexplained. The description does not clarify that it expects an ASN number or its format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'ASN allocation record' is a noun phrase without a verb, leaving ambiguity about the tool's action (e.g., lookup, list, describe). It vaguely identifies the subject but does not clearly state what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not mention when to use this tool versus siblings like 'domain' or 'ip', nor suggests any prerequisites or constraints.

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

All Rdap toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

The RDAP tools (domain, ip, asn, nameserver, entity) are distinct, but the larger Pipeworx collection creates significant overlap: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates, and the polymarket_* family (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread) has heavily overlapping purposes. ai_visibility_check and scan_competitor_ai_presence also overlap.

Naming Consistency3/5

Most tools use snake_case with a descriptive verb_noun pattern (e.g., ask_pipeworx, discover_tools, recent_changes), but the set mixes short single nouns (domain, ip, asn, entity) with compound names, and there are oddities like generate_llms_txt and ask_pipeworx_grounded that deviate from a clear uniform convention.

Tool Count2/5

At 36 tools, the server is far heavier than expected for an RDAP service. The RDAP core only needs ~5 tools; the rest are an unrelated Pipeworx mega-suite (data queries, prediction markets, memory, subscriptions, feedback) that makes the server feel like a dumping ground rather than a focused toolset.

Completeness4/5

For the RDAP portion, coverage is complete: domain, IP, ASN, nameserver, and entity records are all present. The broader Pipeworx features also cover their own workflows (query, research, comparison, memory CRUD, subscription lifecycle), but the server's stated RDAP identity is muddied by these extras, and some integration points (e.g., no direct update for RDAP data, which is read-only anyway) are inherent limitations.

Resources