Skip to main content
Glama

RICOVANT AI Visibility Auditor

check_ai_crawlers

Free technical checks of public HTML for AI crawler access and readiness

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_crawlers"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP(S) website URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short: it never states that the operation is read-only, that it fetches the URL live, or whether it is rate-limited or cached. Vague 'readiness' also fails to disclose what dimensions are checked, so the agent cannot anticipate the result.

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?

One short, front-loaded sentence with no filler; the key constraint (public HTML) appears immediately. It is efficient, though its brevity leaves information gaps rather than wasted words.

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

Completeness3/5

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

For a simple single-parameter tool this is nearly sufficient, but with no output schema the description should hint at what the checks return. 'Readiness' is left undefined, so an agent cannot judge the result or know how to act on it.

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 the single 'url' parameter is already documented as a public HTTP(S) URI. The description reinforces 'public' but adds no new meaning such as whether redirects, subpaths, or non-HTML responses are accepted, so the baseline of 3 applies.

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 gives a clear verb ('checks') and resource ('public HTML for AI crawler access and readiness'), so an agent knows it inspects a page's crawler-friendliness. It does not differentiate itself from the closely related siblings audit_ai_visibility or check_structured_data, leaving overlap ambiguous.

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

Usage Guidelines2/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 guidance, and no alternative is named despite two adjacent tools in the catalog. The only hint is the word 'Free', which implies a lightweight pre-check but does not state that role.

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