Skip to main content
Glama

Verify a crawler log (real vs forged bots)

verify_crawler_log
Read-onlyIdempotent

Given raw web-server access-log lines, decide for each line that names a crawler (GPTBot, ClaudeBot, Googlebot, PerplexityBot...) whether the source IP falls inside that operator's published ranges. Returns verified, spoofed, or unverifiable when the operator publishes no ranges.

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": {
      "lines": "<lines>"
    },
    "name": "verify_crawler_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYesUp to 200 raw log lines, newline separated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior. The description adds real value beyond them: the verification mechanism (source IP vs published operator ranges) and the three-outcome taxonomy, including the important 'unverifiable' case when no ranges are published. It does not describe the per-line response structure, but annotations' bar is lower.

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?

Two sentences with no waste: input and decision logic are front-loaded, then the output taxonomy is appended compactly. Every sentence earns its place.

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 read-only tool with no output schema, the description covers the decision logic, the classification outcomes, and the key limitation for operators with no published ranges. It lacks a description of the actual return shape, which would help an agent parse results, but the core call rationale is complete.

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 documents the single 'lines' parameter with its 200-line limit. The description adds meaning beyond that schema text by explaining what happens to each line (per-line classification against the named operator) and which crawlers are recognized.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (verify web-server access-log lines that name a crawler) and names the exact decision being made: whether the source IP falls inside the operator's published ranges. It distinguishes itself from siblings like crawler_path or resolve_robots by operating on existing log lines rather than resolving or scanning.

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

Usage Guidelines4/5

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

The input scoping ('Given raw web-server access-log lines') makes the usage context clear: use it when you already have logs to audit. It does not explicitly name alternatives or when-not-to-use conditions, so it stops short of a 5.

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.