Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__generate_llms_txt

Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://pipeworx.io"
    },
    "name": "nsi-bg__generate_llms_txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL of the site to summarize, e.g. "https://example.com" or a specific landing page.
max_linksNoMaximum number of link entries to include (default 25, max 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the internal pipeline (crawl, extract, format) and that output is a single text blob for site-root/llms.txt. It omits the operational realities an agent would want: behavior on unreachable or JS-rendered pages, timeouts, size limits, and whether anything is written to disk or the site itself. Good but incomplete for a network-dependent generator.

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?

Purpose and output are front-loaded, then mechanism, then use cases — a sensible order with quick scanability. Marketing adjectives ("production-ready", "cleanly") are minor filler but not enough to obscure the content.

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 two-parameter, non-destructive-looking generator with no output schema, the description explains what comes back (a markdown text blob ready to drop at site-root) and how it is derived, which is the key information. The remaining gap is failure/edge-case behavior, which keeps it from a 5.

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 description coverage is 100%, so both url and max_links (including the default 25 / max 50 bounds) are already documented there. The description adds no parameter-level meaning beyond reinforcing that any URL or specific landing page is acceptable, so baseline 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 artifact ("generate a production-ready llms.txt file") plus the scope ("for any URL"), and describes the mechanism: fetch the page, extract title/description/key links, emit standard llms.txt markdown. An agent knows exactly what this produces and can distinguish it from a generic page-fetch or summarize tool.

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

Usage Guidelines4/5

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

Gives three concrete usage scenarios (client sites, own project, competitor auditing), which is stronger than most definitions. It stops short of exclusions — nothing says when NOT to use it (e.g. non-HTML pages, JS-only sites, pages already having llms.txt) or what the alternative would be.

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.