Skip to main content
Glama

check_site

Can I scrape this site, and how? Returns a verdict (open, guarded, hostile, blocked), a hostility score, a recommended approach with steps and risks, bot protections, robots.txt and AI-crawler policy, machine-readable surfaces (sitemap, llms.txt, JSON-LD), and eu_ai_training: the signals the EDPB draft Guidelines 03/2026 on web scraping for generative AI count against collecting personal data (robots.txt blocks on AI training crawlers, a Content-Signal of ai-train=no, ai.txt, CAPTCHAs, login walls), as none, some or strong. Signals, not legal advice. Uses a weekly-probed dataset of several hundred sites; for any other domain it probes live from a datacenter IP.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA domain such as reddit.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?

With no annotations, the description does substantial work: it discloses the verdict taxonomy, states that results come from a weekly-probed dataset of several hundred sites and that other domains are probed live from a datacenter IP (a meaningful caveat, since datacenter-origin requests skew bot-protection and CAPTCHA detection versus an agent's own traffic), and adds the 'signals, not legal advice' disclaimer. It does not mention latency or failure behavior for live probes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core question is front-loaded, which is right, and enumerating return fields is justified given there is no output schema. However, the body is one very dense run-on sentence stacking the eu_ai_training clause, dataset provenance, and disclaimers; the EDPB aside could be shortened without losing callable 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?

With no output schema and no annotations, the description carries the return-value burden and does so thoroughly, plus provenance and a legal disclaimer. Remaining gaps are minor for a read-only single-domain lookup: no note on live-probe latency or what a failed probe returns.

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 coverage is 100% and the single parameter is already documented with an example, so baseline is 3. The description earns a bump by explaining that the domain value determines whether a cached weekly-probed record is used or a live probe is performed, which is genuine meaning beyond the schema's 'A domain such as reddit.com'.

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?

Opens with a specific, agent-legible question ('Can I scrape this site, and how?') and enumerates the exact return payload: verdict, hostility score, recommended approach, bot protections, robots.txt/AI policy, machine-readable surfaces. The scope differs from a simple robots check like can_fetch, but the description never names siblings, so the differentiation is inferred rather than stated.

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 use case is implied clearly by the framing question, but there is no explicit when-to-use/when-not, and no routing guidance versus the obvious overlapping sibling can_fetch. The only conditional given is about the underlying data source (weekly-probed dataset vs live probe), which is behavioral rather than usage guidance.

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