Skip to main content
Glama
praveenc

FetchV2 MCP Server

by praveenc

fetch_llms_txt

Need LLM-friendly documentation? Fetch and parse a site's llms.txt file to get a structured list of documentation links in one request.

Instructions

Fetch and parse an llms.txt file to discover LLM-friendly documentation.

USE THIS TOOL WHEN:

  • A site provides an llms.txt file for AI-friendly content discovery

  • You need to understand what documentation is available

  • You want to fetch structured docs in a single request

WHAT IS llms.txt: A proposal for sites to provide LLM-friendly content at /llms.txt. It's a markdown file listing documentation links with descriptions. See https://llmstxt.org for the specification.

WORKFLOW:

  1. fetch_llms_txt(url="https://example.com/llms.txt") → Get structure

  2. Review sections and links

  3. Either use include_content=True or fetch_batch for specific pages

EXAMPLES:

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to an llms.txt file (e.g., https://example.com/llms.txt)
include_contentNoIf true, also fetch content of all linked pages. Default false.
max_length_per_urlNoWhen include_content=True, max chars per linked page. Default 2000.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does a good job: it explains that the tool fetches and parses an llms.txt file, describes the optional include_content behavior, and provides a workflow. It doesn't cover error handling or auth, but for a read-only fetch tool with an output schema, the main behavioral traits are disclosed.

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?

The description is longer than average but well organized into purpose, usage, background, workflow, and examples. Each section adds useful context, and the key action is front-loaded. It could be slightly tighter, but the structure makes it easy to scan.

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 tool with an output schema and clear parameter documentation, the description covers the what, when, and how well, including examples and an alternative path via fetch_batch. It doesn't discuss failure scenarios or rate limits, but nothing essential for a correct first invocation is missing.

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?

Schema coverage is 100%, so the schema already documents all three parameters. The description adds value beyond the schema by providing real-world examples and showing how include_content=True is used in a workflow, which helps an agent understand parameter usage in context.

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 opens with a specific verb+resource pairing: 'Fetch and parse an llms.txt file to discover LLM-friendly documentation.' It clearly distinguishes this from sibling tools by focusing on the llms.txt format and even references fetch_batch in the workflow, so an agent can tell when this tool is the right one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes a dedicated 'USE THIS TOOL WHEN' section listing concrete conditions, and the workflow explicitly names fetch_batch as the alternative for fetching specific pages. This gives an agent clear guidance on when to choose this tool over its siblings.

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

Deploy Server

Other Tools