Skip to main content
Glama

check_llms_txt

Read-only

Validates a site's /llms.txt against the llmstxt.org format and checks robots.txt for blocked AI crawlers. Returns a 0-100 score, fixes, and a draft llms.txt if missing.

Instructions

Check a website's /llms.txt against the llmstxt.org format and its robots.txt for blocked AI crawlers.

Returns a 0-100 score, the problems found with a plain fix for each, and a draft llms.txt built from the site's home page and sitemap when the file is missing. Example input: "example.com".

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": {
      "website": "<website>"
    },
    "name": "check_llms_txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, and the description adds real context beyond them: what the tool fetches (llms.txt, robots.txt, home page, sitemap) and what it returns (0-100 score, problem list with fixes, a draft file when missing). It stops short of saying whether the draft is ever written anywhere or how failures like an unreachable site are surfaced.

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?

Three short sentences with the purpose front-loaded, then return values, then a concrete input example. Every sentence carries information and nothing is padded.

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?

With no output schema, the description correctly takes on the burden of explaining return values, and it does so for a read-only open-world network tool. Remaining gaps are minor, mainly error handling when the site or file is unreachable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single 'website' parameter, so the description must compensate, and it does partially by giving an example input ("example.com") that resolves the domain-vs-full-URL ambiguity. It does not clarify whether a scheme, path, or subdomain forms are accepted.

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 names a specific verb and resource: checking a site's /llms.txt against the llmstxt.org format plus its robots.txt for blocked AI crawlers. The resource is unambiguous and cannot be confused with the sibling check_mcp_server_security, which targets a different artifact.

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 stated scope (auditing AI-crawler readiness for a site) but never stated as when-to-use guidance. There is no mention of prerequisites, no exclusions, and no routing to alternatives, so the agent must infer the scenario.

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

Deploy Server

Other Tools