Skip to main content
Glama
VisualSentinel

Visual Sentinel MCP Server

Official

vs_dns_check

Resolve DNS records for any domain including A, AAAA, MX, NS, TXT, CNAME. No authentication required.

Instructions

Resolve DNS records (A, AAAA, MX, NS, TXT, CNAME) for a domain using Visual Sentinel's public DNS lookup tool. No authentication required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to resolve, e.g. example.com (without protocol).
recordTypeNoOptional: limit to one record type. One of: A, AAAA, MX, NS, TXT, CNAME, SOA. Default: all.

Implementation Reference

  • The handler function for vs_dns_check. It calls the Visual Sentinel public API at GET /api/tools/dns-check with the required 'domain' and optional 'recordType' query parameters. No authentication required.
      handler: async (args, client) =>
        client.request('GET', '/api/tools/dns-check', {
          auth: false,
          query: {
            domain: requireString(args, 'domain'),
            recordType: pickString(args, 'recordType'),
          },
        }),
    },
  • Input schema for vs_dns_check. Defines 'domain' (required string) and 'recordType' (optional string, one of A/AAAA/MX/NS/TXT/CNAME/SOA).
    inputSchema: {
      type: 'object',
      properties: {
        domain: { ...STR, description: 'Domain to resolve, e.g. example.com (without protocol).' },
        recordType: {
          ...STR,
          description: 'Optional: limit to one record type. One of: A, AAAA, MX, NS, TXT, CNAME, SOA. Default: all.',
        },
      },
      required: ['domain'],
      additionalProperties: false,
    },
  • src/tools.ts:65-90 (registration)
    The vs_dns_check tool is registered as one of the tools in the TOOLS array. It is a public tool (requiresAuth: false). The TOOLS array is exported and imported by index.ts, where it is registered with the MCP SDK via ListToolsRequestSchema and CallToolRequestSchema handlers.
    {
      name: 'vs_dns_check',
      description:
        'Resolve DNS records (A, AAAA, MX, NS, TXT, CNAME) for a domain using Visual Sentinel\'s public DNS lookup tool. No authentication required.',
      inputSchema: {
        type: 'object',
        properties: {
          domain: { ...STR, description: 'Domain to resolve, e.g. example.com (without protocol).' },
          recordType: {
            ...STR,
            description: 'Optional: limit to one record type. One of: A, AAAA, MX, NS, TXT, CNAME, SOA. Default: all.',
          },
        },
        required: ['domain'],
        additionalProperties: false,
      },
      requiresAuth: false,
      handler: async (args, client) =>
        client.request('GET', '/api/tools/dns-check', {
          auth: false,
          query: {
            domain: requireString(args, 'domain'),
            recordType: pickString(args, 'recordType'),
          },
        }),
    },
  • Helper function that validates and returns a required string argument from the tool's input args. Used to extract 'domain' in vs_dns_check.
    function requireString(args: Record<string, unknown>, key: string): string {
      const v = pickString(args, key);
      if (!v) throw new Error(`Argument "${key}" (string) is required.`);
      return v;
    }
  • Helper function that safely extracts an optional string argument from the tool's input args. Used to extract 'recordType' in vs_dns_check.
    function pickString(args: Record<string, unknown>, key: string): string | undefined {
      const v = args[key];
      return typeof v === 'string' && v.length > 0 ? v : undefined;
    }
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It states the tool is a 'public DNS lookup tool' and that no authentication is needed, which implies a read-only operation. However, it does not mention rate limits, caching, or error handling. Given the simplicity of DNS lookups, this is minimally transparent.

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?

The description is two sentences that are front-loaded with the main purpose and record types. Every word adds value, and there is no unnecessary information. It is appropriately sized for the tool's simplicity.

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 simple DNS lookup tool with no output schema, the description covers the core functionality and record types. It lacks details on potential errors (e.g., invalid domain, timeout) or the format of the response, but given the low complexity, it is mostly complete. A 4 is appropriate as it could mention response format or limitations.

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 100%, so the input schema already describes both parameters adequately. The description adds no additional meaning beyond what the schema provides (e.g., the list of record types is present in both). Thus, it meets the baseline for a well-documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Resolve DNS records'), the resource ('a domain'), and lists specific record types (A, AAAA, MX, NS, TXT, CNAME). This differentiates it from siblings like vs_ssl_check and vs_website_check, which focus on SSL and website status respectively.

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 description mentions 'No authentication required,' which provides some context but does not explain when to use this tool vs. alternatives (e.g., vs_website_check for HTTP availability, vs_ssl_check for certificate checks). There is no explicit when-not or when-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VisualSentinel/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server