Skip to main content
Glama

net_tools_dns_lookup

[$x402 pago por llamada] Resuelve un registro DNS para un host, vía dig. Rechaza hosts con caracteres fuera de [a-zA-Z0-9.-] (protección contra inyección de flags).

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

Input Schema

NameRequiredDescriptionDefault
hostYes
typeNoTipo de registro: A, AAAA, MX, TXT, NS, CNAME o SOA. Por defecto 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.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the x402 pay-per-call model, the 402 response when payment is omitted (consistent with the x_payment schema field), and an input-validation rule rejecting characters outside [a-zA-Z0-9.-] as flag-injection protection. It stops short of describing error behavior for failed resolution or the shape of the DNS answer.

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 sentences, both front-loaded with the essentials: payment model and resolution behavior first, then the validation constraint. No filler, though the bracketed payment tag is slightly cryptic in placement.

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 3-parameter lookup with no output schema, the description covers purpose, cost, and input safety, but says nothing about what the successful response contains (record values, TTL, resolver used), which an agent cannot infer from the schema.

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 67%, and the description compensates by stating the host validation charset, which the schema leaves as a bare string. The record type and payment parameters are already documented in the schema, so no further credit is owed there.

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: 'Resuelve un registro DNS para un host, vía `dig`', which is clearly distinct from net_tools_whois_lookup, net_tools_ping and net_tools_asn_lookup. It does not explicitly name a sibling alternative, so it stops 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?

The purpose implies when to use it (resolve a DNS record for a host), but there is no explicit guidance on when to prefer it over whois_lookup, ping, or ssl_check, nor any stated prerequisites for the paid call beyond the bracketed payment note.

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