Skip to main content
Glama

net_tools_asn_lookup

[$x402 pago por llamada] Resuelve el ASN, prefijo, país y nombre de la organización dueña de una IP/host, vía Team Cymru (whois-over-DNS).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>"
    },
    "name": "net_tools_asn_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesHostname o IPv4. Si es hostname, se resuelve a IP primero (registro A).
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does add real context: this is a metered x402 paid call and the data comes from Team Cymru over DNS. It does not say what happens with private/unroutable IPs, non-resolving hostnames, or whether results are cached, so the mutation-adjacent cost behavior is only half-explained.

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?

A single compact sentence with a bracketed payment tag; no wasted words. The payment tag leading the sentence is slightly ahead of the core purpose, but the whole thing is short enough that nothing is buried.

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?

There is no output schema and no annotations, so the description usefully names the four returned fields (ASN, prefix, country, org name) and the payment precondition. It is nearly complete for a two-parameter lookup, missing only failure-case behavior for unresolvable hosts.

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 both `host` and `x_payment` are already documented in the schema, including the A-record resolution behavior and the 402 fallback. The description adds nothing about parameter semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb (resolves) and precise outputs (ASN, prefix, country, org name) for a specific input (IP/host), plus the data source (Team Cymru whois-over-DNS). It never distinguishes itself from the neighboring net_tools_whois_lookup, so an agent facing an IP-ownership question has no stated rule for choosing between them.

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?

Usage is only implied by the input scope: 'de una IP/host' tells the agent this is for IP ownership resolution, and the payment tag signals the x402 flow. There is no explicit when-to-use/when-not-to-use guidance and no mention of net_tools_whois_lookup or net_tools_dns_lookup as alternatives.

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