Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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

A4.1/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does reasonably well: it discloses the fetch-and-extract pipeline (title/description/key links), the output format (standard llms.txt markdown, single text blob), and the intended destination path. It omits operational behavior an agent might need — what happens on fetch failure, JS-rendered pages, timeouts, or rate limits — so it is solid but not complete.

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?

The core capability is front-loaded in the first sentence, followed by mechanism, output, and use cases in a logical order with no filler sentences. There is minor redundancy between "so AI crawlers... can index the site cleanly" and the "getting a client's site indexed by AI" use case, which keeps it just under top marks.

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?

With only two parameters, no annotations, and no output schema, the description supplies what matters: the input (any URL), the processing, and the exact return shape (one markdown text blob at site-root/llms.txt). The remaining gap is failure/edge-case behavior on un-fetchable pages, which is not addressed.

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` are already documented with examples and defaults in the schema, making 3 the baseline. The description adds only the loose phrase "key links," which hints at the link-selection parameter without clarifying semantics beyond what the schema states.

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?

The description opens with a specific verb and artifact: "Generate a production-ready llms.txt file for any URL," then names the audience (AI crawlers) and the mechanism (fetch, extract, emit standard markdown). An agent can tell exactly what comes out — a single text blob drop-in for site-root/llms.txt — without opening the schema.

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?

It gives three concrete usage scenarios (getting a client's site indexed, drafting your own llms.txt, auditing a competitor's AI visibility), which is clear positive guidance for when to reach for it. It stops short of any exclusion or prerequisite, such as noting it is unnecessary when the site already publishes an llms.txt, so it misses the 5 mark.

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.