Skip to main content
Glama
Sign In

HTTPfy network & DNS tools

by io.httpfy
OverviewDiscussionsAdmin

ASN lookup

asn_lookup
Read-onlyIdempotent

Look up the autonomous system (ASN) for a public IP address, or details for an ASN such as AS15169: name, country, announced prefixes and address counts.

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": {
      "query": "<query>"
    },
    "name": "asn_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesIP address or ASN (8.8.8.8 or AS13335)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 the useful constraint that the IP must be public and describes what the result contains (prefixes and address counts), which matters because there is no output schema; it stops short of noting private/reserved ranges or lookup failures.

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?

A single sentence that front-loads the primary action and then the secondary mode, with no filler. Both branches (IP to ASN, ASN to details) are stated compactly.

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 rich annotations, the definition covers the input shapes and the shape of the answer, which compensates for the absent output schema. Minor gaps remain around error or not-found behavior, but nothing essential is missing.

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?

With 100% schema coverage the parameter is already fully documented, including the same format examples ('8.8.8.8 or AS13335'). The description restates the same example format (AS15169) without adding syntax rules, normalization behavior, or handling of invalid inputs, so it sits at the baseline.

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 and resource ('look up the autonomous system') and enumerates the returned fields (name, country, announced prefixes, address counts), which is more than a restatement of the name. It does not explicitly distinguish itself from the related ip_whois sibling, so it falls short of a 5.

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: it accepts a 'public IP address' or an ASN, which hints at acceptable inputs but gives no guidance on when to pick this over ip_whois or dns_lookup, nor any exclusions or prerequisites. The agent must infer the choice from the input format.

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

All HTTPfy network & DNS tools 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