Skip to main content
Glama
geo-seo-readiness-lite

geo-seo-readiness-lite

check_llms_txt

Read-only

Fetches a site's /llms.txt and verifies it is valid Markdown with a title, sections and links, flagging HTML soft-404s so you know AI crawlers can parse it.

Instructions

Fetch /llms.txt for the site and check that it is Markdown with a title, sections and links (detects HTML soft-404s).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic page or site URL, e.g. https://example.com/pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds real behavior: it fetches a fixed path and applies structural validation, including catching HTML soft-404s served with a 200. It stops short of stating what happens on network failure, redirects, or non-200 responses.

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?

A single sentence carries the action, the target path, the validation criteria, and the key failure mode with no filler. The most decision-relevant content (what is fetched) comes first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must convey what comes back; it implies structural findings but never says whether the result is a boolean, a list of failed checks, or raw content. For a one-parameter read-only check that gap is tolerable but real.

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 100%, so the baseline is 3, but the description adds a meaningful clarification: the fetch targets /llms.txt at the site level, resolving the ambiguity in the schema example that shows a /pricing page URL. It does not clarify whether a deep link is normalized to the root or the path is ignored.

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?

States a specific verb pair (fetch, check) plus the exact resource (/llms.txt) and defines the pass criteria: Markdown with a title, sections and links. That resource specificity also separates it from siblings like check_sitemap and check_ai_crawler_access without needing to name them.

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 — an agent can infer this is the verification step for a site's llms.txt, and the parenthetical 'detects HTML soft-404s' signals one failure mode. There is no explicit statement of when to prefer this over check_sitemap or quick_readiness_report, and no prerequisites noted.

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