Skip to main content
Glama

AEGIS (McX Ventures)

DNS lookup and hijack check

dns_check
Read-only

DNS resolution and hijack check for one domain — resolver answers with private-address and anomaly flags Price: $0.002 USDC on Base per call, paid with x402.

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": {
      "target": "<target>"
    },
    "name": "dns_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesPublic hostname (not an IP address), e.g. example.com

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?

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the return shape (resolver answers plus private-address and anomaly flags), the one-domain-per-call limit, and — importantly — the paid x402 model with a concrete price in USDC on Base. It does not cover failure behavior (NXDOMAIN, timeouts), but the payment requirement is meaningful context annotations cannot express.

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?

One compact sentence that front-loads the action and result, followed by the pricing constraint. Slightly dense with em-dash chaining, but every element (scope, output flags, payment) carries information.

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 single-parameter, no-output-schema tool, the definition covers what the tool does, what the response contains, and the cost/payment prerequisite. Remaining gaps are modest: no mention of error or non-resolving-domain behavior, and no sense of rate limits or latency.

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 coverage is 100% and the single parameter already documents 'Public hostname (not an IP address)'. The description only restates the one-domain scope, adding no format, normalization, or edge-case detail beyond the schema, so the baseline of 3 applies.

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 a specific verb pair (DNS resolution and hijack check) and a bounded scope (one domain), plus what the response contains (resolver answers with private-address and anomaly flags). It is clearly distinct from certificate/TLS siblings by resource, though it does not explicitly name an alternative.

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: an agent can infer this is the tool for inspecting a domain's DNS records and detecting suspicious resolutions. There is no explicit when-to-use versus ct_check/tls_check guidance and no stated exclusions or prerequisites beyond the schema's hostname-only constraint.

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