Skip to main content
Glama

Nyt

by io.github.pipeworx-io

Generate llms.txt

generate_llms_txt
Read-onlyIdempotent

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.

Input Schema

TableJSON 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).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive nature. The description adds behavioral details: fetches page, extracts title/description/key links, emits standard llms.txt format. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded paragraph with no wasted words. Every sentence adds value: purpose, process, and use cases.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 2 parameters, full schema coverage, no output schema, and rich annotations, the description adequately explains the output format and use cases. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers 100% of parameters with descriptions. The description supplements by giving an example URL format and default/max values for max_links, adding meaningful context beyond the schema.

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 uses a specific verb 'generate' and resource 'llms.txt file', and clearly distinguishes from sibling tools like 'scan_competitor_ai_presence' by specifying the unique output format and use case.

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 description explicitly lists three use cases (getting a client's site indexed, drafting for own project, auditing competitor), providing clear context for when to use the tool. It does not state when not to use, but the guidance is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nyt toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

ask_pipeworx and ask_pipeworx_beta are explicitly identical today, and ask_pipeworx_grounded, deep_research, and validate_claim all route to the same underlying sources with overlapping question-answering purposes. Entity-focused tools like entity_profile, compare_entities, recent_changes, and resolve_entity also have fuzzy boundaries that make selection error-prone.

Naming Consistency2/5

Names mix conventions: verb_noun (list_subscriptions, search_articles, generate_llms_txt), bare verbs (remember, recall, forget), noun phrases (polymarket_arbitrage, pipeworx_trending, entity_profile), and an ask_* family with beta/grounded variants. There is no consistent verb or noun pattern across the set.

Tool Count2/5

With 35 tools, the surface is well above the 15-tool threshold for a focused server, and most tools are unrelated to the NYT domain implied by the server name. The breadth reflects a broad data-platform grab bag rather than a scoped, intentional tool set.

Completeness4/5

The query side is unusually complete: single-lookup, grounded lookup, deep research, claim validation, entity resolution, comparison, profile, change-feed, discovery, memory, and subscription lifecycle tools are all present. Minor gaps remain, such as no direct NYT article fetch by URL and no update path for stored memories, but agents can work around them.

Resources