Skip to main content
Glama

BRAINIAC Public Infrastructure Lookups

Map IP or prefix to origin ASN

public-infrastructure_ip-to-asn-lookup
Read-onlyIdempotent

Longest-prefix match against a vendored RouteViews BGP snapshot, with IANA special-purpose flags. Price $0.02 USDC. POST /api/v1/public-infrastructure/ip-to-asn-lookup. 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_ip-to-asn-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNoip, string, length 3 to 64. Optional.
prefixNoprefix, string, length 3 to 64. Optional.

Output Schema

NameRequiredDescriptionDefault
queryNoquery. String.
matchedNomatched. Object.
sourcesNosources. Array.
coveringNocovering. Array.
snapshotNosnapshot. Object.
attributionNoattribution. String.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already cover safety traits such as read-only and idempotent, and the description adds substantial context beyond them: the data source is a vendored RouteViews snapshot, results include IANA special-purpose flags, the call costs $0.02 USDC, and unpaid calls return x402 terms without running.

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 short and front-loaded: the lookup mechanism comes first, followed by price, endpoint, and unpaid-call behavior. Every sentence adds relevant operational context without filler.

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

Completeness3/5

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

For a simple lookup with an output schema, the description covers the data source and payment flow well. However, it leaves important input semantics unresolved: both parameters are optional, and the description does not say whether one is required or how conflicting ip and prefix values are handled.

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%, so the schema already documents the two optional parameters. The description adds the idea of matching an IP or prefix but does not clarify formats, mutual exclusivity, or what happens if neither parameter is supplied.

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 states a specific mechanism, longest-prefix match against a RouteViews BGP snapshot, and mentions IANA special-purpose flags. It does not explicitly state that the result is an origin ASN, relying on the title/name for the outcome, and does not differentiate from sibling lookup tools.

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?

There is no guidance on when to use this tool versus alternatives, nor on when to use ip versus prefix. The payment behavior is described, but that is invocation mechanics rather than usage selection guidance.

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