Skip to main content
Glama
Sign In
ShieldDNS MCP server

ShieldDNS MCP server

Official
by shielddns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Check a domain or link

check_domain
Read-onlyIdempotent

Check a domain or URL for safety before opening it. Returns a verdict, risk score with reasons, and advice to guide safe browsing.

Instructions

Check whether a domain or URL is safe to open, using the ShieldDNS protective resolver. Returns a verdict (blocked, dnssec_invalid, does_not_exist, resolves...), a 0-100 risk score with human-readable reasons (blocklist match, DNSSEC, look-alike of known brands, mixed scripts, random-looking names) and an advice field (ok_to_open, caution, do_not_open). Accepts a bare domain or a full URL.

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": {
      "domain_or_url": "<domain_or_url>"
    },
    "name": "check_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_or_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description adds genuinely new behavioral context by enumerating the verdict values, the risk signals evaluated, and the advice field. It stops short of stating rate limits, latency, or behavior on malformed input.

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, front-loaded with the purpose and followed by the return contract; the parenthetical lists are dense but each item is informative. Slightly list-heavy, but no filler sentences.

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?

With no output schema, describing the verdict, risk score, reasons and advice field is exactly the missing information, and the accepted input form is covered too. Only minor gaps remain, such as error handling and whether results are cached.

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 description coverage is 0% and the single property has no title-level detail, so the description carries the burden — and it does, explicitly stating it accepts either a bare domain or a full URL. That is the key ambiguity an agent would otherwise face, though input normalization rules (e.g. schemes, ports, trailing paths) remain unstated.

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 opens with a specific verb and resource ('Check whether a domain or URL is safe to open') and names the underlying resolver, which distinguishes it from the plain 'resolve' sibling. It is clear what the tool produces, though it never explicitly contrasts itself with 'resolve' or 'service_status'.

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: 'safe to open' suggests a pre-visit safety screen rather than raw resolution, which hints at the boundary with 'resolve'. There is no explicit when-to-use/when-not statement and no named alternative, leaving the agent to infer routing between siblings.

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

Deploy Server

Other Tools