Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

generate_llms_txt

Creates machine-readable llms.txt and llms-full.txt files from a sitemap or website root so AI assistants and LLM crawlers can discover and interpret site content.

Instructions

Generate a compliant machine-readable llms.txt and llms-full.txt specification for AI assistants and LLM crawlers from a sitemap or website root.

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": {
      "sitemap_url": "<sitemap_url>"
    },
    "name": "generate_llms_txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_urlsNoMaximum number of page links to include (default: 30)
brand_nameNoProduct or brand name for the header title
sitemap_urlYesURL to the sitemap.xml or website root (e.g., 'https://example.com/sitemap.xml')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and falls short. It never says whether the tool crawls the live site, what permissions or rate limits apply, or whether generated files are returned, written to disk, or deployed — all critical for a generation tool that may touch a live site.

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 front-loaded sentence with the verb and deliverables first and the input source last; there is no filler or redundancy.

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?

With three well-documented parameters and no output schema or annotations, the definition covers the input side adequately but leaves the outcome underspecified: what the agent receives back (file contents, URL, written files) and whether side effects occur on the target site are not stated.

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?

Schema coverage is 100%, so the baseline is 3. The phrase 'from a sitemap or website root' mirrors the sitemap_url schema text rather than extending it, and nothing is added about max_urls or brand_name behavior.

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 ('Generate') and concrete artifacts ('llms.txt and llms-full.txt specification'), plus the input source ('sitemap or website root'). Naming the llms.txt artifacts distinguishes it in kind from siblings like generate_robots_txt and generate_schema_json, though the description never explicitly routes between them.

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 mention of alternatives among the generation siblings (robots.txt, schema JSON). The only implied usage is the choice of input source, which is already captured by the parameter.

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