Skip to main content
Glama

GEO & SEO Readiness (Lite)

audit_ai_search_readiness

Read-onlyIdempotent

Audit a public http/https URL for AI search readiness: robots.txt rules (OAI-SearchBot, PerplexityBot, ClaudeBot, GPTBot, Googlebot), /llms.txt soft-404 detection, non-JS HTML title/description/canonical, JSON-LD schema types, and prioritized fix_first actions.

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": "audit_ai_search_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic website URL to audit (e.g., https://example.com).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered structurally. The description adds genuine value beyond that by disclosing the specific artifacts inspected (live robots.txt, /llms.txt, rendered-vs-non-JS HTML) and that output includes prioritized fix_first actions. It stops short of noting timeouts, rate limits, or whether the fetch is live versus cached.

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?

A single front-loaded sentence with zero filler, leading with the verb and object before the checklist. The parenthetical bot list and comma-separated checks make it dense, but each item conveys a distinct capability an agent could use for routing decisions.

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 audit tool with no output schema, the description covers what is examined and hints at the response shape via 'prioritized fix_first actions.' Only the overall response structure and any fetch-time constraints remain unstated, which is a minor gap given the rich annotations.

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?

With one parameter at 100% schema description coverage, the schema already carries the burden of documenting 'url'. The description adds only the 'public http/https' constraint and the enumerated checks, which give context on what the URL is used for but no additional syntax or format guidance.

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?

States a specific verb (audit) and resource (a public http/https URL) and enumerates exactly what is inspected: robots.txt user-agent rules, llms.txt soft-404, non-JS metadata, JSON-LD types, and fix_first actions. This clearly delimits it as a single-URL audit rather than the sibling's two-domain comparison, though it never names that alternative explicitly.

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?

Usage is only implied through the phrase 'public http/https URL,' which conveys that internal/authenticated URLs are out of scope. There is no explicit statement of when to pick this over compare_two_domains_readiness, nor any prerequisites or failure conditions.

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.