Skip to main content
Glama

NS Pros MCP Gateway

nist-fluid-properties__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": "nist-fluid-properties__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
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 it does disclose the key behaviors: it performs an outbound fetch of the target page, extracts metadata, and returns a single text blob. It omits failure behavior for unreachable or blocked URLs, any rate limiting, and whether the fetch is cached, which leaves real gaps for a network-touching tool.

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 action and artifact, then mechanism, then use cases. Slightly promotional phrasing like "production-ready" and the parenthetical list of AI crawlers is expendable but not costly.

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 utility with a fully documented schema and no structured output, the description supplies what the schema cannot: the return shape (a text blob placed at site-root/llms.txt) and the fetch behavior. Only error handling is left undescribed.

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 and max_links documented including the default of 25 and the cap of 50. The description adds the notion that "key links" are extracted, which gives context for max_links, but does not itself specify formats or limits, so the schema does the heavy lifting.

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?

"Generate a production-ready llms.txt file for any URL" gives a specific verb and artifact, and the follow-up sentence explains the mechanism (fetch, extract, emit). It is unmistakably clear what the tool produces, though it offers no differentiation from the many identically-named siblings, leaving the namespace prefix to carry that distinction.

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 names three concrete scenarios (client site indexing, drafting for your own project, auditing a competitor's crawl view), which tells the agent when this is the right call. It stops short of stating when not to use it or naming an alternative for retrieval-only needs.

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.