Skip to main content
Glama

Verify an AI crawler's IP address

verify_crawler_ip
Read-onlyIdempotent

Check whether an IP address really belongs to an AI or search crawler (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Googlebot, Bingbot, Applebot, Amazonbot) using the vendors' published IP lists (refreshed daily) and reverse DNS. Use this when someone sees a crawler in server logs or analytics and wants to know whether it is real or a fake user agent; pass the log line's user agent to check the claim.

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": {
      "ip": "<ip>"
    },
    "name": "verify_crawler_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesThe visitor's IP address (IPv4 or IPv6)
user_agentNoThe user agent from the same log line, to check which crawler it claims to be

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, so safety is covered; the description adds the meaningful extra context of data provenance and freshness ('vendors' published IP lists (refreshed daily) and reverse DNS'). It does not mention rate limits, latency, or failure/unknown-result behavior, but the output schema carries the return shape.

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, front-loaded with the core operation and the methods, followed by the usage scenario. The parenthetical bot list is long but serves disambiguation value; no filler sentences.

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 low-complexity, 2-parameter read-only lookup with an output schema, the description covers what it does, how it verifies, and when to reach for it. Only minor gaps remain (behavior on unknown/reserved IPs, and explicit sibling alternatives).

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?

Schema coverage is 100% and both parameters are documented inline (IP as IPv4/IPv6, user agent from the same log line). The description's note about passing the log line's user agent restates rather than extends that, so baseline 3 is appropriate.

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 ('Check whether an IP address really belongs to an AI or search crawler') and enumerates the covered bots plus the verification sources (vendor IP lists + reverse DNS). This distinguishes it cleanly from sibling inventory/activity tools such as list_ai_crawlers or get_crawler_activity.

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?

Gives a concrete trigger scenario ('someone sees a crawler in server logs or analytics and wants to know whether it is real or a fake user agent') and tells the agent to pass the log line's user agent. It stops short of explicitly ruling out nearby siblings (e.g., check_ai_crawlers), so no exclusion guidance.

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.

Resources