Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

domain_site

Read-only

Fetch one public HTTPS homepage using validated public DNS answers and a pinned IP connection that preserves Host and TLS SNI. Return the TLS certificate, allowlisted response headers, and local technology fingerprints from that page.

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 public DNS hostname such as github.com; do not include a scheme, path, port, or IP address.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only mark it read-only and open-world; the description adds substantial behavior: resolution is limited to validated public DNS answers, the connection is pinned to that IP while preserving Host header and TLS SNI. It also discloses what is returned (certificate, allowlisted headers, local tech fingerprints). It does not cover rate limits, timeouts, or failure behavior.

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?

Two sentences with the operation and its constraints front-loaded, then the outputs. Dense but each clause carries information; the DNS-pinning/SNI detail is technical yet behaviorally relevant rather than filler.

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 one-parameter fetch tool with an output schema and safety annotations, the description covers mechanism, output, and input constraints adequately. Remaining gaps (timeouts, redirect handling, error modes) are minor given the structured fields already 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?

With a single parameter and 100% schema description coverage, the schema already explains the bare-hostname format and the no-scheme/path/IP rule. The description's 'public HTTPS homepage' framing reinforces validity constraints but adds no new parameter-level detail.

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?

Names a specific verb and resource ('Fetch one public HTTPS homepage') and scopes it tightly to a single root page rather than arbitrary URLs. It never names or contrasts with siblings like domain_dns_resolve, domain_robots, or web_techstack, so an agent must infer the boundary from other context.

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

Usage Guidelines2/5

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

The 'one public HTTPS homepage' phrasing implicitly rules out deep paths, non-HTTPS, and private hosts, which is some guidance. However, there is no explicit when-to-use statement and no named alternative for adjacent needs such as DNS-only lookups, robots.txt, or tech-stack profiling via web_techstack.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources