Skip to main content
Glama

NS Pros MCP Gateway

noaa-ndbc__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": "noaa-ndbc__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.6/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. It does disclose the pipeline (fetches the page, extracts title/description/key links, emits standard markdown) and the return shape ('a single text blob ready to drop at site-root/llms.txt'), which is genuinely useful. However it says nothing about network failure behavior, whether it renders JavaScript-heavy pages, rate limits, or how much of the page gets read — meaningful gaps for a fetch-and-summarize 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?

Front-loaded with the core action and output, followed by the mechanism and then use cases — a sensible ordering. The 'Useful for' list is somewhat padded and could be trimmed, but each clause does convey distinct information.

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 read-style tool with full schema coverage and no output schema, the description covers purpose, mechanism, output format, and placement of the result. Remaining omissions (error handling, crawl fidelity limits) are relatively minor but keep it from being complete.

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%: both `url` and `max_links` are documented in the schema, including the default of 25 and max of 50. The description adds no parameter-level detail beyond that and never mentions `max_links`, so the baseline 3 applies.

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?

The first sentence states a specific verb and artifact — 'Generate a production-ready llms.txt file for any URL' — plus the intended consumer (AI crawlers). It also explains the mechanism (fetch page, extract title/description/links). It does not differentiate from the many sibling `generate_llms_txt` tools, though those appear to be the same operation replicated per data source, so there is little real ambiguity to resolve.

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?

'Useful for:' enumerates three concrete scenarios (client site indexing, drafting for your own project, competitor auditing), which gives an agent a clear sense of when this tool fits. It stops short of explicit exclusions or when-not-to-use conditions, so it is not a full 5.

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.