Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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 behavioral load and does well: it discloses that a live fetch occurs, what gets extracted, the output format, and that the result is a single text blob meant to be dropped at site-root. It omits failure behavior for unreachable or JS-rendered pages and any rate-limit or auth caveats, which keeps it from a 5.

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 front-loaded sentences with no filler: purpose and behavior first, output shape second, use cases last. Minor redundancy between "so AI crawlers can index the site cleanly" and the list of named crawlers, but nothing that wastes meaningful space.

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?

There is no output schema, so the description appropriately explains the return value as a ready-to-deploy llms.txt text blob, which is what an agent needs to decide and act. The remaining gap is edge-case behavior on fetch failures or non-HTML targets, which matters for a tool whose core operation is a network fetch.

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. The description adds only the notion of scope ("any URL"), while the default-25/max-50 behavior of `max_links` lives entirely in the schema. This is the expected baseline when the schema does the heavy lifting.

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 for any URL." It also names the mechanism (fetch, extract title/description/key links, emit standard markdown), so the agent knows exactly what it produces. The sibling list contains only same-named variants from other providers, so no further differentiation is needed.

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:" sentence gives three concrete usage contexts (client site indexing, drafting your own, competitor audit), which is clear when-to-use guidance. It stops short of explicit when-not conditions or prerequisites such as needing the URL to be publicly reachable, but the intended invocation context is unambiguous.

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.