Skip to main content
Glama

AI Visibility Audit

Check AI crawler access and llms.txt

check_ai_crawler_access
Read-onlyIdempotent

Check which AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and others) a site's robots.txt allows or blocks, and whether its /llms.txt exists and is valid. Returns a shareable result page on https://serp.tsoden.ai.

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": {
      "url": "<url>"
    },
    "name": "check_ai_crawler_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe website to check, e.g. https://example.com or example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), and the description adds real value beyond them by enumerating the crawlers checked and disclosing that the output is a shareable result page hosted at serp.tsoden.ai. It stops short of mentioning rate limits, caching, or when the generated page expires.

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, both front-loaded: the first names exactly what is inspected, the second states what comes back. 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 one-parameter read-only check with full annotation coverage, the description is close to complete: it says what is examined and that a shareable result page is returned, which substitutes for the missing output schema. Minor gaps remain around what 'valid' llms.txt means and how long the result page persists.

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?

There is a single required parameter with 100% schema description coverage, including accepted formats (https://example.com or example.com) and a max length. The description adds no syntax or normalization detail beyond the schema, so the baseline of 3 is correct.

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: checks which named AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended) robots.txt allows or blocks, plus whether /llms.txt exists and is valid. This is concrete enough to separate it from audit_ai_readiness and check_schema_readiness without opening any schema.

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?

The scope (robots.txt and /llms.txt of a single site) implicitly tells the agent what this tool covers, but there is no explicit when-to-use statement, no prerequisites, and no pointer to the sibling audit_ai_readiness for broader assessments. Usage must be inferred from the described scope.

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