Skip to main content
Glama

AI Crawler Permission Check

Which AI crawlers may fetch this site

check_ai_crawlers
Read-onlyIdempotent

For a domain (and optional path), whether each known AI crawler/agent user-agent is allowed by robots.txt, with the deciding rule.

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": {
      "site": "<site>"
    },
    "name": "check_ai_crawlers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
siteYes

Output Schema

NameRequiredDescriptionDefault
agentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and network-touching behavior are covered. The description adds genuinely useful context beyond that: the rules come from robots.txt and the response includes the deciding rule per crawler. It does not say whether robots.txt is fetched live, cached, or what happens when it is missing/unreachable.

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?

One sentence, front-loaded with the scope (domain plus optional path) and immediately followed by the outcome and the extra payload. No filler, no restatement of the title.

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 two-parameter read-only lookup with an output schema and full annotation coverage, the description supplies what an agent needs: the input scope, the data source (robots.txt), per-crawler granularity, and the returned deciding rule. Only input formatting conventions are left unstated.

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 description coverage is 0%, so the description carries the burden. It does clarify that 'site' is a domain and 'path' is optional, which is real meaning beyond the bare string schema, but it never specifies the expected domain format (bare host vs. scheme/URL) or how the path should be formed, leaving the main ambiguity unresolved.

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 check (robots.txt allow/deny evaluation) against a specific resource class (known AI crawler user-agents), plus the extra detail that the deciding rule is returned. It is clear what the tool does, but it never distinguishes itself from the sibling check_user_agent, so the agent must infer the boundary.

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?

There is no explicit when-to-use or when-not-to-use sentence, and no mention of the sibling as an alternative. The scenario (auditing whether AI crawlers are permitted for a site/path) is implied by the purpose statement itself, which lands at 'implied usage' rather than real 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