Skip to main content
Glama

ai_visibility_check

Score a domain 0-100 for AI crawler readiness: robots.txt rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended and CCBot, plus llms.txt, sitemap.xml, JSON-LD and indexability, with three concrete fixes. Use when asked whether AI assistants can read, cite or recommend a site.

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": {
      "domain": "<domain>"
    },
    "name": "ai_visibility_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose the scoring range and that three concrete fixes are returned, plus which site artifacts are inspected, but it does not state that the operation is read-only, whether it fetches the live domain, or any latency/rate-limit behavior. The name "check" and the inspection list imply a safe read, but that is inference rather than disclosure.

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?

The definition is two tight sentences: the first front-loads what is scored and the full checklist, the second states the triggering use case. Every clause contributes and there is no filler.

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 check tool with no output schema, the description sufficiently explains the deliverable (a 0-100 score plus three fixes) and the inspected artifacts. It is only marginally incomplete in not clarifying read-only/network behavior, which matters because no annotations are present.

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 one required parameter and schema coverage is 100%, with the schema itself supplying the domain-name format example. The description adds no further parameter semantics beyond what the input schema already provides, so the baseline of 3 applies.

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 ("Score"), a bounded resource (a domain), an explicit output range (0-100), and an enumerated checklist covering robots.txt crawler rules, llms.txt, sitemap.xml, JSON-LD and indexability. That detail distinguishes it from generic siblings such as site_audit or seo_snapshot, which are not framed around AI crawler readiness.

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?

It states a clear triggering context: "Use when asked whether AI assistants can read, cite or recommend a site." That is enough to route an agent here rather than to robots_txt or http_head, though it does not explicitly name an alternative or a when-not-to-use condition.

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