Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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, the description carries the full burden and does disclose the important behaviors: it makes an outbound fetch of an arbitrary URL, performs extraction, and returns a single text blob in standard llms.txt markdown intended for site-root placement. Not disclosed are failure behavior for unreachable pages, fetch/render limitations, rate limits, or any cost/latency expectation — gaps that matter for a tool that may be pointed at third-party URLs.

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?

Three sentences, front-loaded with the outcome before the mechanics and the use cases. Slightly padded by marketing adjectives ("production-ready", "cleanly", "ready to drop") and a use-case list that partly repeats the opening sentence's AI-crawler framing.

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 no output schema, the description correctly compensates by specifying the return shape ("a single text blob ready to drop at site-root/llms.txt" in standard markdown), which is what an agent most needs here. Minor incompleteness on error handling and on whether the page must be publicly reachable, but the essential contract is covered.

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%, with both `url` (full URL, example given) and `max_links` (default 25, max 50) documented inline, so the schema already does the work. The description adds only indirect context — "extracts title/description/key links" hints at what max_links governs — without stating truncation or formatting behavior when the cap is hit.

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?

"Generate a production-ready llms.txt file for any URL" gives a specific verb (generate) and resource (llms.txt) plus the operating scope (any URL). The second sentence expands exactly what the generation entails: fetch the page, extract title/description/links, emit standard markdown. An agent knows precisely what it gets back.

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?

The "Useful for:" clause supplies three concrete situations (client site indexing, own project drafting, competitor auditing), which is real when-to-use guidance rather than a restatement of the name. It stops short of any when-not or exclusion criteria — nothing says what to do if the URL is JS-rendered, robots-restricted, or already has an llms.txt.

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.