Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

AI crawler IP ranges

ayrank_ai_crawler_ip_ranges
Read-only

Fetch published CIDR ranges for major AI crawlers to verify real bot hits in server logs and detect fake traffic; sources show live or dated snapshots.

Instructions

Use to get the CIDR ranges that OpenAI, Perplexity, Anthropic, Google, Bing, Apple, Common Crawl and Mistral publish for their crawlers and agents, for example to tell a real GPTBot hit in server logs from a fake one. Each source says whether it is live or a dated snapshot. Cached for 24 hours. No input. Not for checking whether a bot may crawl a site (use ayrank_ai_crawler_access).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ayrank_ai_crawler_ip_ranges"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the 24-hour cache (relevant freshness expectation) and that each source is flagged as live or a dated snapshot, which tells the agent how to interpret the payload. It also notes there is no input, so the call profile is fully predictable.

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?

Three tight sentences, front-loaded with the purpose, then the freshness caveat, then the exclusion. Every clause carries information an agent would otherwise have to guess at.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must convey the return shape, and it does: per-source CIDR lists plus a live-vs-snapshot label. For a zero-parameter, read-only lookup, nothing needed to call it correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4. 'No input' confirms the empty schema rather than adding meaning, which is the only reason this is not higher.

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?

The description gives a specific verb and resource — 'get the CIDR ranges' — names the exact publishers (OpenAI, Perplexity, Anthropic, Google, Bing, Apple, Common Crawl, Mistral), and states a concrete use case (separating real GPTBot hits from fakes in server logs). It also explicitly differentiates from the sibling ayrank_ai_crawler_access, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Both directions are covered: when to use it ('to tell a real GPTBot hit in server logs from a fake one') and when not to ('Not for checking whether a bot may crawl a site (use ayrank_ai_crawler_access)'), with the alternative named. No inference is required.

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