Skip to main content
Glama

Check a site's llms.txt and llms-full.txt files

llms_txt
Read-only

Whether a site publishes /llms.txt and /llms-full.txt: the parsed llms.txt (title, summary, sections with their links) and the size of llms-full.txt. Reads the site itself, through the same URL guard and size cap as the page tools. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
urlYesSite address, https://…

Output Schema

NameRequiredDescriptionDefault
siteNo
sourceNo
llmsTxtNo
llmsFullNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that it fetches the remote site, that it is subject to the same URL guard and size cap as the page tools, and that reads of llms-full.txt are bounded. It also gives the cost model explicitly: $0.002 per successful call via x402 (USDC on Base, Solana and more), with failed calls uncharged. The only remaining gap is what failure/absence of the files looks like, which the output schema largely covers.

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?

Two sentences, front-loaded with what is returned and then the operational constraints and price. Nothing is padded, and the pricing detail is worth its space for a paid call. The first sentence is a verbless fragment, which costs a bit of readability.

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?

For a single-parameter read tool with an output schema and safety annotations, the description covers the essentials: what is fetched, the guard/cap behavior, and the billing terms. Return-shape detail is present but not required given the output schema. Only the missing selection guidance against sibling tools keeps it short of full completeness.

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 required parameter, url, and schema coverage is 100% with the schema already giving an example format ('Site address, https://…'). The description adds only the implicit point that the URL is a site address whose own /llms.txt path is probed, so it does not materially extend parameter meaning beyond the schema. Baseline 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?

The description names the exact artifacts it inspects (/llms.txt and /llms-full.txt) and what it returns (parsed title, summary, sections with links, plus the size of llms-full.txt). That is a specific verb-plus-resource statement that an agent can distinguish from siblings like links or web_security_txt. The opening is a grammatical fragment ("Whether a site publishes...") rather than a clean verb phrase, which slightly blunts it.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. An agent must infer from the resource name alone that this is the tool for checking AI-crawler guidance files rather than invoking links, ai_crawlers, or a generic page fetch. Usage is implied by the description but not 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