Skip to main content
Glama

diogenes-web-scraping-engine-mcp

HTML Table to Structured JSON & Markdown Parser

parse_html_tables
Read-onlyIdempotent

Detects and parses HTML table elements from live URLs or raw HTML into structured JSON record arrays and GitHub-Flavored Markdown tabular grids. Accepts either 'url' to fetch directly or raw 'html_content' from upstream scrape_readable_article; for extracting full article body text, use scrape_readable_article instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'url' or 'html_content' ('output_format' defaults to 'markdown_and_json'), supports '?demo=true' or L402 (10 sats), and returns HTTP 400 if invalid.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "parse_html_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOptional web page URL to fetch and parse directly, bypassing an out-of-band fetch step.
min_rowsNoMinimum rows required for a table to be parsed and retained.
html_contentNoRaw HTML string containing one or more table, thead, tbody, or tr elements.
output_formatNoTabular export formatting standard: markdown and JSON, JSON records only, or CSV string.

Output Schema

NameRequiredDescriptionDefault
tables_foundYesCount of valid HTML tables detected and transformed.
markdown_tablesYesList of GitHub-Flavored Markdown formatted table strings.
structured_recordsYesParsed array of row objects keyed by header column titles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "Optional web page URL to fetch and parse directly, bypassing an out-of-band fetch step.",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "html_content"
      -]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing statelessness, a 32 KB payload cap, a 60 RPM rate limit, L402 payment (10 sats) or ?demo=true access, and HTTP 400 on invalid input — operationally critical facts an agent cannot infer from readOnlyHint/idempotentHint. The only residual gap is that fetching arbitrary live URLs sits awkwardly with openWorldHint=false, leaving network-egress expectations slightly ambiguous.

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 purpose and the sibling exclusion are front-loaded in the first two sentences, which is good ordering. The final sentence is an over-packed run-on that crams rate limits, payment, defaults and error codes into nested parentheses, costing some readability without adding fluff.

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?

With an output schema present, return values need no explanation, and the description covers access model, limits, defaults and failure mode. Nothing essential for a correct call is missing, though the min_rows retention behavior is left entirely to the schema.

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 the schema already documents all four parameters and the baseline is 3. The description adds some routing meaning (url vs html_content, the default for output_format) but says nothing about min_rows, the retention threshold, leaving that entirely to 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?

States a specific verb and resource ('detects and parses HTML table elements') plus the two output shapes (JSON record arrays, GFM tables). It also names the sibling it is not ('for extracting full article body text, use scrape_readable_article instead'), so an agent can separate it from scrape_readable_article and extract_clean_markdown without reading schemas.

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?

Explicitly lays out the two input routes — 'url' to fetch directly versus 'html_content' from upstream scrape_readable_article — and names a concrete alternative with the condition that selects it. It even specifies a fallback path (upstream article tool feeding html_content), which is more than most siblings offer.

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.

Resources