Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Website to Clean AI Markdown & llms.txt Converter

convert_website_to_ai_markdown_llms_txt
Read-onlyIdempotent

Converts webpage URLs into clean LLM-ready Markdown, token-counted RAG chunks, and /llms.txt index entries for AI ingestion.

Instructions

Convert webpages into clean LLM-ready Markdown, token-counted RAG chunks, and /llms.txt index entries ($0.50/1k).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "urls": "<urls>"
    },
    "name": "convert_website_to_ai_markdown_llms_txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesWebpage URLs to convert to clean AI Markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing pricing ($0.50/1k) and the three output formats, but it omits operational traits such as URL limits per call, crawl depth versus single-page behavior, JS rendering, or latency.

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?

A single front-loaded sentence that packs outputs and price with no filler. The dense phrasing ('token-counted RAG chunks') is informative rather than redundant, though the pricing parenthetical competes slightly with the core purpose statement.

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

Completeness3/5

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

For a one-parameter, non-destructive converter with full annotation coverage and no output schema, most of what an agent needs is present. However, the description leaves open the meaningful unknowns of batching behavior across multiple URLs and what the response actually contains given three distinct output types, which matters for a paid, open-world tool.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3. The description does not add meaning beyond the schema: it does not clarify whether 'urls' means individual pages only or site-wide crawling, nor any URL format constraints.

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 description uses a specific verb ('Convert') and resource ('webpages') and enumerates three concrete output artifacts: clean LLM-ready Markdown, token-counted RAG chunks, and /llms.txt index entries. That output profile is clearly distinct from the sibling tools, which are mostly lead-scraping and SEO audit tools, though the description never explicitly contrasts itself with any named alternative.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for turning pages into LLM-consumable text, but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative. Nothing tells the agent whether to pick this over a generic scrape tool in the sibling list.

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