Skip to main content
Glama
Sign In

HTTPfy network & DNS tools

by io.httpfy
OverviewDiscussionsAdmin

IP WHOIS

ip_whois
Read-onlyIdempotent

WHOIS / registry data for a public IPv4 address: ASN, network range, owner organisation and registry.

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": {
      "ip_address": "<ip_address>"
    },
    "name": "ip_whois"
  }
}

Input Schema

NameRequiredDescriptionDefault
ip_addressYesIP Address (Enter IP address)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description usefully adds that only public IPv4 is supported and lists the returned fields, but says nothing about rate limits, lookup failures, or unallocated ranges.

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 compact sentence that front-loads the resource and ends with the payload contents. Every clause earns its place and nothing is repeated from the title alone.

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 annotation coverage and no output schema, the description covers input scope and result contents adequately. Only minor gaps remain around failure modes and alternate tools for domains or ASNs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single required parameter, so the baseline is high. The description still adds meaning by qualifying the address as public IPv4, which constrains valid input beyond the schema's generic 'IP Address' label.

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 (WHOIS/registry data) and the scope (a public IPv4 address), then enumerates the returned fields (ASN, network range, owner org, registry). The 'IPv4' qualifier implicitly separates it from domain_whois, though it never names that sibling explicitly.

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 through the 'public IPv4 address' constraint. There is no explicit statement of when to choose this over domain_whois or asn_lookup, and no note about what to do for private/reserved addresses or hostnames.

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