Skip to main content
Glama

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.

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": {
      "asn": "AS15169"
    },
    "name": "as_overview"
  }
}

Input Schema

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

Output 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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds that results include AS type (transit/content/IXP) and allocation date, but this field list largely overlaps the output schema and adds no operational caveats such as rate limits or lookup failures for unallocated ASNs.

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?

Compact, single-paragraph description with the core purpose stated early. The four quoted user-query fragments are somewhat repetitive padding, but they are short and aid recognition rather than obscuring the substance.

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?

For a one-parameter read-only lookup with full schema coverage, rich annotations, and a present output schema, the description supplies everything needed to call it correctly: what question it answers, what the result covers, and accepted input formats. Only sibling disambiguation is absent.

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 parameter is already documented with its own example, so the description's "Pass 'AS15169' or '15169'" restates what the schema provides. The added value is only confirming both prefixed and bare formats are accepted, which is marginal.

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?

The description names the resource (Autonomous System Number) and the specific operation (summary), and enumerates what the summary contains: holder organization, country, AS type, and allocation date. It does not directly differentiate from siblings like asn_neighbours or prefix_overview, but the scope is unambiguous.

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?

"Use for network attribution, BGP analysis" implies the right context but gives no explicit when-not guidance or mention of alternatives such as asn_neighbours for adjacency data. The quoted example queries help an agent recognize matching asks, but that is query matching, not usage routing.

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.