Skip to main content
Glama

Ripe Stat

by io.github.pipeworx-io
OverviewDiscussionsAdmin

As Overview

as_overview
Read-onlyIdempotent

"Who owns AS[N]" / "AS[number] info" / "what company is ASN [X]" / "Cloudflare / Google / Amazon ASN" — summary for an Autonomous System Number (ASN): holder organization, country, AS type (transit / content / IXP), allocation date. Pass "AS15169" or "15169". Use for network attribution, BGP analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asnYesAS number (e.g. "AS15169" or "15169")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoASN summary with holder, country, type, and block range
statusNoAPI response status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "asn": "AS15169"
+  },
+  {
+    "asn": "3356"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "ASN summary with holder, country, type, and block range",
+      "type": "object"
+    },
+    "status": {
+      "description": "API response status",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds behavioral context by listing the exact fields returned (holder, country, type, date), which goes beyond annotations and helps the agent understand what to expect.

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?

The description is two sentences plus example queries in quotes. It is front-loaded with the most common use-case queries, and every part contributes to understanding the tool. No redundant or missing information.

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

Completeness5/5

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

With only one parameter and an output schema available, the description provides sufficient context: it lists the output fields and usage. The tool is simple and the description covers all necessary aspects for correct invocation.

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% with a clear description of the 'asn' parameter. The description adds examples and alternative formats ('AS15169' or '15169'), but this is already implied by the schema. Baseline is 3 because schema does the heavy lifting; description provides marginal additional value.

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

Purpose5/5

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

The description starts with natural language queries like 'Who owns AS[N]' and 'AS[number] info', then clearly states it returns a summary for an ASN: holder organization, country, AS type, allocation date. It distinguishes itself from siblings like 'asn_neighbours' by focusing on overview rather than neighbors or BGP state.

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

Usage Guidelines4/5

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

The description provides example queries and explicitly says 'Use for network attribution, BGP analysis.' It does not explicitly exclude alternatives, but the context makes it clear when to use this tool. Minor improvement would be to mention siblings like 'asn_neighbours' for neighbor information.

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

All Ripe Stat 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