agentwebmap

Check llms txt

check_llms_txt

Read-onlyIdempotent

Validate a site's llms.txt: reachability, HTML-instead-of-text, redirects to other domains, H1 title, summary, sections, links, link health, llms-full.txt and charset. Returns each check with what to fix and the file preview. Ownership management is optional and does not affect validation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	A domain name such as example.com (no scheme, no path).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

addedInput schema / properties / domain / maxLength
```
Added value: +253
```
addedInput schema / properties / domain / minLength
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "bytes": {
+          "type": "integer"
+        },
+        "checked_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "checks": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "detail": {
+                "type": "string"
+              },
+              "label": {
+                "type": "string"
+              },
+              "ok": {
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "ok",
+              "label",
+              "detail"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "content_hash": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "domain": {
+          "type": "string"
+        },
+        "http_status": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "listed": {
+          "anyOf": [
+            {
+              "additionalProperties": false,
+              "properties": {
+                "authority": {
+                  "type": [
+                    "integer",
+                    "null"
+                  ]
+                },
+                "page": {
+                  "type": "string"
+                },
+                "status": {
+                  "enum": [
+                    "pending",
+                    "valid",
+                    "invalid",
+                    "unreachable"
+                  ],
+                  "type": "string"
+                },
+                "tier": {
+                  "enum": [
+                    "featured",
+                    "listed",
+                    "unlisted",
+                    "rejected",
+                    null
+                  ],
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "verified": {
+                  "type": "boolean"
+                }
+              },
+              "required": [
+                "status",
+                "tier",
+                "authority",
+                "verified",
+                "page"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "max": {
+          "type": "integer"
+        },
+        "parsed": {
+          "additionalProperties": false,
+          "properties": {
+            "linkCount": {
+              "type": "integer"
+            },
+            "sectionCount": {
+              "type": "integer"
+            },
+            "summary": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "title": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "title",
+            "summary",
+            "sectionCount",
+            "linkCount"
+          ],
+          "type": "object"
+        },
+        "plausible": {
+          "type": "boolean"
+        },
+        "preview": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "score": {
+          "type": "integer"
+        },
+        "url": {
+          "type": "string"
+        },
+        "verdict": {
+          "enum": [
+            "valid",
+            "unreachable",
+            "needs work"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "domain",
+        "url",
+        "checks",
+        "score",
+        "max",
+        "listed",
+        "verdict",
+        "preview"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": true,
+      "properties": {
+        "detail": {
+          "type": "string"
+        },
+        "domain": {
+          "type": "string"
+        },
+        "error": {
+          "type": "string"
+        },
+        "hint": {
+          "type": "string"
+        },
+        "retry_after_seconds": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedOct 18, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so safety is covered. The description adds real value beyond them: the full set of checks, that results include remediation guidance ('what to fix'), and a file preview. It stops short of describing pagination or failure modes.

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?

Three sentences, front-loaded with the purpose, then the check list, then the ownership caveat. The middle list is dense but each item is meaningful scope information rather than 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?

An output schema exists, so return values need not be explained; the description nonetheless notes the response shape (per-check results, fixes, preview). For a read-only validation tool with full annotation and schema coverage, this is nearly complete, lacking only explicit sibling routing.

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 a single parameter and 100% schema description coverage, the schema already documents the domain format (no scheme, no path). The description adds no parameter-level detail, 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?

States a specific verb+resource ('Validate a site's llms.txt') and enumerates the exact checks performed, so an agent knows the scope precisely. It does not name or explicitly contrast with the nearest sibling (generate_llms_txt), so it falls short of full sibling differentiation.

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 implied by the name and check list, and the closing note that 'Ownership management is optional and does not affect validation' preempts a likely confusion. However, there is no explicit when-to-use, when-not-to-use, or named alternative, leaving routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agentwebmap tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.