Skip to main content
Glama

net_tools_whois_lookup

[$x402 pago por llamada] Consulta WHOIS de un dominio. Devuelve la salida cruda del registro, sin parsear.

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_whois_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
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

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose two important traits: the call is paid ('$x402 pago por llamada') and the output is raw, unparsed WHOIS text. However, it omits error behavior, what happens on payment failure beyond the schema's hint, and any rate or permission details.

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?

Two short sentences, front-loaded with the payment notice and then the core action and output shape. No wasted words, though the payment bracket could arguably be separated for clarity.

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 lookup tool with no output schema and no annotations, the description covers the essential action, output form, and payment requirement. It is still thin on error handling and does not clarify the domain input format or any optional behavior, leaving gaps an agent might need filled.

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 50%: the x_payment parameter is documented in-schema, but the required 'host' parameter has no schema description. The description's phrase 'de un dominio' partially compensates by clarifying that host is a domain name, adding marginal meaning over the bare schema.

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 verb and resource ('Consulta WHOIS de un dominio') and adds a clear output trait ('salida cruda del registro, sin parsear'). It does not explicitly differentiate from siblings such as net_tools_dns_lookup or net_tools_asn_lookup, but the WHOIS resource is unique enough that an agent can identify the tool's purpose.

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?

It says what the tool does but gives no guidance on when to use it versus alternatives like dns_lookup or asn_lookup, nor any preconditions beyond the payment note. The agent must infer usage from the resource name alone.

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