Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

domain_site

Inspects an HTTPS homepage by resolving its hostname via DoH, rejecting unsafe addresses, pinning the connection with Host/SNI, and returning TLS, header, and technology data from one bounded response.

Instructions

Inspect one public HTTPS homepage. Resolves the hostname through public DoH, rejects unsafe addresses, pins the connection while preserving Host and TLS SNI, then derives TLS, public headers, and technology from one bounded homepage response.

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

Input Schema

NameRequiredDescriptionDefault
domainYesBare DNS hostname

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/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 behavioral burden and does well: it discloses DoH hostname resolution, unsafe address rejection, connection pinning, preservation of Host and TLS SNI, and bounded single-response behavior. It omits details such as timeout, redirect handling, exact response limits, and failure behavior, so it is strong but not complete.

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 description is a single dense sentence with zero filler and is front-loaded with the core action. Every clause adds relevant scope or behavioral 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?

Given one required parameter and no output schema, the description provides enough operational context for selection and invocation, including safety and data-derivation behavior. It could be more complete by indicating return shape or key limitations, but it is largely adequate for this tool's complexity.

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?

The only parameter, domain, has a fully covered schema description ('Bare DNS hostname'). The description refers to resolving 'the hostname' but does not add syntax, format, or validation detail beyond what the schema already states.

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 states a specific verb and resource: inspect one public HTTPS homepage and derive TLS, header, and technology information. This clearly identifies the purpose, though it does not explicitly distinguish the tool from adjacent DNS or homepage-adjacent siblings.

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 'Inspect one public HTTPS homepage' and the derived outputs, giving enough signal for selection. However, the description does not state when to use this instead of alternatives, nor does it provide explicit exclusions or prerequisites.

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