QueryRev AI Readiness
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| checkA | Checks how a site treats AI crawlers: which of the covered crawlers robots.txt lets in, whether /llms.txt is a real llms.txt, what the home page says without scripts, its structured data and its sitemap. Requests up to four public files, only where robots.txt allows this tool; takes up to 30 seconds. The result is JSON, schemaVersion 1, the same as |
| robots_testA | Says which robots.txt line decides for a crawler token and a path (RFC 9309). Give url to read a site's robots.txt, or text to test a robots.txt you already have, with no request. Without agent every covered crawler is tested. The result is JSON, schemaVersion 1, the same as |
| llms_validateA | Checks an llms.txt against llmstxt.org: one H1, a summary, sections of links. An HTML page or a robots.txt served at /llms.txt is reported as not being one. Give url to read a site's file, or text to validate a file you already have. links also requests up to 20 of its links. The result is JSON, schemaVersion 1, the same as |
| llms_generateA | Builds the skeleton of an llms.txt from the site's own sitemap, or the links on its home page. Pages that say noindex, redirect elsewhere or are closed to this tool by robots.txt are left out. Titles and descriptions are the pages' own words; the file is a draft to edit, and nothing is written to disk: the text is in the result. Takes up to 120 seconds (a site's own crawl delay counts); with a progress token the client gets a notification after each request, and cancelling the call stops the requests. The result is JSON, schemaVersion 1, the same as |
| crawlersA | Lists the AI crawlers this server checks, with vendor and purpose (training, search or user fetch), and says which crawlers are covered. Makes no request. The result is JSON, schemaVersion 1, the same as |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The five tools have mostly distinct roles: an aggregate audit (check), a focused robots.txt line matcher (robots_test), an llms.txt validator, an llms.txt generator, and a static crawler registry. The only real overlap is that `check` subsumes some robots.txt and llms.txt inspection that robots_test and llms_validate perform in depth, but the descriptions make the aggregate-vs-deep-dive boundary clear.
Three tools follow a clear noun_verb pattern (robots_test, llms_validate, llms_generate), but `check` is a bare verb and `crawlers` a bare noun, so the pattern is not predictable across the set. Readable, but an agent cannot infer a name from a new operation.
Five tools is well matched to a narrow AI-readiness auditing domain, with each tool covering a distinct artifact (robots.txt, llms.txt validation, llms.txt generation, crawler list, full audit). Nothing appears redundant or padded.
The surface covers the core lifecycle: enumerate crawlers, test robots rules, validate and generate llms.txt, and run a combined audit. Minor gaps exist in that structured-data and sitemap analysis are only reachable through the aggregate `check`, with no dedicated or configurable operation for them.