Skip to main content
Glama

Scan a site for AI and crawler readiness

scan_domain

Scan a public domain as several crawler identities and return the graded record: grade, AI-visibility score, per-section scores, findings with evidence, and whether the origin refused CrawlCheck. One scan takes 5-15 seconds.

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_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA bare domain such as example.com, or a full URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare openWorldHint=true, destructiveHint=false, idempotentHint=false, and readOnlyHint=false, so the description does not need to restate safety metadata. The description adds useful behavioral context beyond those annotations: it scans as several crawler identities, reports whether the origin refused CrawlCheck, and notes that one scan takes 5-15 seconds. It still does not explain auth requirements, rate limits, or why readOnlyHint is false, but it is stronger than the baseline.

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 definition is two sentences, front-loaded with the core action and followed by the return shape and timing. Every phrase contributes directly to selection or invocation, with no redundant wording or buried 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?

For a single-parameter tool with no output schema, the description supplies the essential return contents, scan duration, and the crawler-identity context. It omits some operational details such as error behavior or assumptions about invalid domains. Overall it is complete enough for an agent to invoke the tool correctly.

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 only one parameter and schema description coverage is 100%, so the schema already defines that domain accepts a bare domain or full URL. The description adds the constraint that the domain should be public, which is minor additional meaning. Beyond that, it does not add syntax, validation, or edge-case guidance for the parameter.

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 clearly states a specific verb and resource: scanning a public domain as several crawler identities for AI and crawler readiness. It also enumerates the graded record returned, which makes the tool's purpose concrete. It does not explicitly differentiate itself from nearby siblings such as check_site_safety or preflight, so it falls short of the highest clarity score.

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 implies when to use the tool by describing a domain-wide AI and crawler readiness scan with a graded record. However, it gives no explicit when-to-use versus when-not-to-use guidance and does not name alternatives among the many sibling tools. The implied context is adequate but leaves selection between overlapping tools to inference.

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.