Skip to main content
Glama

Observed crawler path on a site

crawler_path

Where each crawler's path into a domain dies, as an observed data flow: edge decision, robots.txt as a file, robots.txt rules, then the page, JSON-LD, sitemap, llms.txt and entitymap.json it reached. Give agent (e.g. ClaudeBot, GPTBot, googlebot) for one identity's path and a one-line answer; omit it for every identity plus the stores and breaks. Uses the latest record on file, or scans first when there is none (fresh=true forces a scan). The answer-engine output is drawn but never measured.

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

Input Schema

NameRequiredDescriptionDefault
agentNoIdentity id or label, e.g. claudebot, GPTBot, Googlebot
freshNoScan now instead of using the record on file
domainYes

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?

Beyond the annotations it discloses real behavior: the tool reads the latest record on file, falls back to scanning when none exists, and fresh=true forces a scan — which explains why readOnlyHint is false and idempotentHint is false. It also adds a data-quality caveat ('the answer-engine output is drawn but never measured'). It does not cover cost, duration, or failure modes of the scan path.

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?

Front-loaded but dense: the opening sentence is a long run-on enumeration of pipeline stages, and the closing line ('drawn but never measured') is cryptic shorthand. Every sentence carries information, but phrasing like 'where each crawler's path into a domain dies' costs clarity without adding precision.

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 three parameters, no output schema, and only partial schema coverage, the description carries much of the burden and mostly does: it describes the traced artifacts, the per-identity vs all-identity result shapes, and the record-vs-scan sourcing. The undescribed domain parameter and the opaque closing line are the remaining gaps.

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 67%, with agent and fresh already documented in the schema. The description still adds meaningful semantics the schema lacks: omitting agent changes the result to every identity plus 'the stores and breaks', and the record-vs-scan default for fresh is spelled out rather than just 'scan now'. The domain parameter remains undescribed in both places.

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 names a specific resource — the observed crawler path into a domain — and enumerates the exact stages it traces (edge decision, robots.txt file, robots.txt rules, page, JSON-LD, sitemap, llms.txt, entitymap.json). That specificity makes it distinguishable from record-reading siblings like machine_record or verify_crawler_log, though it never names a sibling explicitly.

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?

It gives parameter-level usage guidance ('give agent for one identity's path and a one-line answer; omit it for every identity plus the stores and breaks'), which implies what each mode is for. However it offers no when-to-use-this-vs-alternatives guidance among the many sibling tools (scan_domain, verify_crawler_log, machine_record), and no exclusions or prerequisites.

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.