Skip to main content
Glama

BRAINIAC Telecom & Network Infrastructure Intelligence

Diagnose DNS resolution

network-intelligence_dns-resolution-diagnose

Diagnose caller-supplied DNS answers against expected values, or optionally query key-free public DNS for a public hostname. Price $0.03 USDC. POST /api/v1/network-intelligence/dns-resolution-diagnose. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "network-intelligence_dns-resolution-diagnose"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
logsNo
textNo
filesNo
configsNo
bgpRoutesNo
incidentsNo
publicDnsNo
publicTlsNo
dnsRecordsNo
reputationsNo
certificatesNo
latencySamplesNo
latencyAnomalyZNo
expiryWarningDaysNo
packetLossSamplesNo
packetLossWarnPctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With zero annotations, the description carries the full burden. It usefully discloses pricing ($0.03 USDC), the payment gate (402 and no execution on unpaid calls), and the endpoint. It does not state whether the operation is read-only, what the response contains, or any rate limits — meaningful gaps for a diagnostic tool with no annotation safety profile.

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?

Three short sentences with no filler, and the core capability is front-loaded ahead of cost and transport details. It is efficient, though slightly too terse for the breadth of the input schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex (20 params, nested objects, no required fields) with no output schema and no annotations. The description covers the two headline modes and billing but omits how the many optional input families relate to the diagnosis, which an agent needs in order to build a correct call.

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

Parameters2/5

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

Schema description coverage is 0% across 20 parameters. The description hints at only two of them implicitly (dnsRecords for caller-supplied answer/expectedAnswer comparison, publicDns for the live lookup) and says nothing about csv, logs, configs, bgpRoutes, incidents, reputations, certificates, or the various tuning parameters. For a 20-param tool with no schema documentation, this leaves the input shape largely unexplained.

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: 'Diagnose caller-supplied DNS answers against expected values', and names an optional mode ('query key-free public DNS'). That is clearly distinct from siblings like certificate-expiry or latency-anomaly. It stops short of explicitly naming an alternative tool, but the purpose itself is unambiguous.

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?

It distinguishes two operating modes (caller-supplied answers vs. live public DNS lookup for a public hostname), which implies when each path applies. There is no explicit when-not guidance, no prerequisites spelled out, and no routing to siblings when another tool would fit better.

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