Skip to main content
Glama
SLF Guardian MCP

SLF Guardian MCP

by slfguardian

scan_site

Run a passive outside-in website security check to detect malware and spam traces, hidden redirects, SSL/TLS issues, exposed versions and missing SPF/DMARC; returns a score, grade and findings.

Instructions

Passive outside-in security check of a website: malware and spam injection traces, hidden redirects, SSL/TLS certificate state, security headers, exposed software versions and SPF/DMARC email spoofing protection. Does not log in, does not run attack tests. Returns a score out of 100, a grade and findings by category.

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": "<domain>"
    },
    "name": "scan_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain or URL, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it declares the scan is passive and outside-in, requires no login, and performs no attack tests, which tells the agent this is non-intrusive and safe to call against third-party sites. Gaps remain around runtime, rate limits, or whether repeated calls are throttled.

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?

Two sentences, front-loaded with the operation and followed by its coverage list and scope limits, then a single line on the return shape. Every clause carries information and nothing is redundant.

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?

Even without an output schema, the description tells the agent what comes back (score out of 100, a grade, findings by category), which is what an agent needs to decide to call it. Minor omissions are operational details such as expected latency and whether calls are rate-limited.

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?

There is a single required parameter with 100% schema description coverage ('Domain or URL, e.g. example.com'), so the schema already does the heavy lifting. The description adds only the implicit notion that the target is a website domain, with no extra format or normalization detail beyond the schema example.

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 names a specific verb and resource ('Passive outside-in security check of a website') and then enumerates exactly what is inspected: malware/spam injection, hidden redirects, SSL/TLS state, security headers, exposed versions, SPF/DMARC. That enumeration makes it clearly distinct from a sibling like check_domain, which would not cover site-level injection and header checks, so an agent can select without opening the schema.

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 implied by the scope statement rather than stated: an agent can infer 'use this to vet a website's security posture.' The 'does not log in, does not run attack tests' line is a scope exclusion rather than routing guidance, and no sibling tool is named as an alternative for overlapping needs such as domain registration checks.

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