Skip to main content
Glama

AgenticCart: AI readiness checks for online stores

Check a site's llms.txt

check_llms_txt
Read-onlyIdempotent

Fetch a website's /llms.txt and check it against the llmstxt.org format: the H1 title, the summary block, the link sections, whether the listed links answer, and whether the server really sends the file rather than an HTML page. Returns a 0-100 score with findings; when the file is missing it says so. Use this when asked whether a site has an llms.txt, whether it is valid, or how to improve it. For a whole-store review use check_store_readiness, which only notes whether the file exists.

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
urlYesThe website URL, e.g. "https://example.com". Any page of the site works; the file is read from the site root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real value beyond them: the 0-100 scoring output, the missing-file behavior, and the notable check that the server actually serves the file rather than an HTML page. Not credit-eligible for a 5 only because it doesn't note failure modes for unreachable sites or how link-checking affects runtime.

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 tight sentences: what it does, what it returns, and when to use it versus the sibling. The behavioral and routing information is front-loaded with no filler or repetition of the title.

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

Completeness5/5

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

With no output schema available, the description carries the return-value burden and does so: a 0-100 score with findings, plus the explicit missing-file case. Combined with the 100%-covered single parameter and the annotated safety profile, nothing an agent needs to call this correctly is absent.

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?

There is a single parameter at 100% schema description coverage, and the schema already explains that any page URL works because the file is read from the site root. The description adds no further meaning about the url argument, so the baseline of 3 applies.

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 and resource ("Fetch a website's /llms.txt and check it against the llmstxt.org format") and enumerates exactly what is validated: H1 title, summary block, link sections, link reachability, and content-type. This distinguishes it cleanly from check_store_readiness, which is described as merely noting file existence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger conditions ("Use this when asked whether a site has an llms.txt, whether it is valid, or how to improve it") and names the alternative plus the condition that selects it ("For a whole-store review use check_store_readiness, which only notes whether the file exists"). Both sides of the routing decision are stated.

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.

Resources