Skip to main content
Glama

Ripestat Asn Search

ripestat_asn_search
Read-onlyIdempotent

"What is [company]'s ASN" / "find the AS number for [organisation]" / "search ASNs by name", resolve an organisation or network name to its AS numbers and prefixes using RIPEstat's resource autocomplete. Returns candidate ASNs with their holder descriptions, so it is the lookup step BEFORE as_overview / ripestat_announced_prefixes / asn_neighbours when you only know the company name. Matches on the registered AS name and holder description across all five RIRs.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "cloudflare"
    },
    "name": "ripestat_asn_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesOrganisation or network name to search for (e.g. "cloudflare", "deutsche telekom")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: it returns candidate ASNs with holder descriptions (i.e., possibly multiple ambiguous matches rather than one) and matches on registered AS name and holder description across all five RIRs, which explains the breadth of results. It stops short of stating result caps or what an empty result means.

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?

Front-loaded with concrete user phrasings, then the purpose, then the sequencing advice — a sensible order. Three quoted example intents plus a fairly long final sentence make it denser than strictly necessary, but no sentence is redundant.

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?

For a one-parameter, read-only lookup with full annotation coverage and no output schema, the description supplies everything needed: what it resolves, what it returns, how matching works, and where it sits in a multi-step workflow.

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 parameter, so the baseline is 3. The description adds a little meaning by framing the input as an organisation or network name and listing example queries, but the same examples already appear in the schema, and no format or normalization guidance (e.g., handling of legal suffixes) is provided.

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?

States a specific verb and resource — resolving an organisation or network name to AS numbers and prefixes — and pins the mechanism (RIPEstat resource autocomplete). It names the sibling tools it feeds into (as_overview, ripestat_announced_prefixes, asn_neighbours), so the agent can distinguish it from them without opening any schema.

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

Usage Guidelines5/5

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

Explicitly positions itself as "the lookup step BEFORE as_overview / ripestat_announced_prefixes / asn_neighbours when you only know the company name," giving both the condition and the downstream alternatives. The quoted example phrasings ("What is [company]'s ASN", "search ASNs by name") map directly onto typical user intents.

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.