Skip to main content
Glama
SLF Guardian MCP

SLF Guardian MCP

by slfguardian

check_domain

Verify a domain/link before opening, sharing data, or installing via registration age, DNS, typosquatting, and phishing signals; returns safe-to-trust and safe-to-open verdicts without site contact.

Instructions

Check a domain or link before opening it, sending data to it or installing from it. Uses the public registration record and DNS: registration age, registry status, whether it resolves, lookalike and typo-squatted brand names, a brand hidden in a subdomain, punycode and mixed-script hostnames, link shorteners, disposable hosting, abuse-heavy TLDs and phishing wording. Returns a verdict with safe_to_trust and safe_to_open. The site itself is never contacted.

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": "check_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoDomain or full URL.
domainsNoCheck several in one call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.9/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 well: it names the data sources (public registration record and DNS), states the non-invasive property ('The site itself is never contacted'), and describes the verdict shape (safe_to_trust, safe_to_open). It omits operational traits such as rate limits, latency, or failure behavior for unresolvable inputs.

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?

It is front-loaded with purpose, then method, then return values, then the safety note, which is a sensible order. The long signal enumeration is dense but each item conveys real capability, so little is wasted, though it could be trimmed without loss.

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 read-only inspection tool with no annotations and no output schema, the description covers inputs' intent, data sources, non-invasiveness, and the two verdict fields. The gap is that both parameters are optional with no required flag, and the description never states that at least one of domain/domains must be supplied.

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 both parameters are already documented in the schema, and the description adds no syntax, format, or precedence rules beyond that. It does not explain the batch parameter ('domains') or what happens if both are supplied, leaving the baseline 3 appropriate.

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 definition opens with a specific verb+resource ('Check a domain or link') and enumerates exactly what signals are evaluated, so the agent knows the scope without opening the schema. It implicitly separates itself from scan_site via 'The site itself is never contacted', but it never names that sibling or check_package, which the 'installing from it' phrasing overlaps with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear situational triggers: before opening a link, sending data to it, or installing from it. That is genuine when-to-use guidance rather than an implied purpose. It stops short of explicit when-not conditions or naming an alternative tool to route to.

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