Skip to main content
Glama

Extract every HTML table of a web page as JSON

tables
Read-only

Every HTML table of a web page as JSON: caption, headers and rows, up to 10 tables with 200 rows each. Tables that a script draws are not included. robots.txt is respected; a page it disallows answers 403, not charged. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "url": "<url>"
    },
    "name": "tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesWeb page address, e.g. https://example.com/page

Output Schema

NameRequiredDescriptionDefault
urlNo
noteNo
sourceNo
tablesNo
checkedAtNo
tableCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses concrete output limits (up to 10 tables, 200 rows each), rendering exclusions (no script-drawn tables), robots.txt behavior including the 403 response, and the billing model ($0.002 per successful call, failures not charged). Those are exactly the operational facts an agent needs before spending money on a call.

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?

Three compact sentences, front-loaded with the output contract, followed by limitations and then cost — a sensible order with almost no filler. The pricing/network detail is dense but genuinely earns its place as decision-relevant information.

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 single-parameter, paid, open-world extraction tool, the definition covers output shape, hard limits, rendering caveats, robots handling, and cost. With an output schema present, no return-value explanation is required, and nothing material is missing.

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 coverage is 100% for the single required 'url' parameter, so the schema already documents the only input. The description adds nothing about URL form, redirects, or page-type suitability, leaving parameter handling entirely to the schema — the baseline 3 for fully-covered schemas.

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 names a specific resource and output shape: 'Every HTML table of a web page as JSON: caption, headers and rows,' which lets an agent tell it apart from adjacent extraction siblings like headers or extract. The verb is carried by the title ('Extract') rather than the description itself, and no sibling is named explicitly, so it falls just short of a 5.

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?

It gives clear negative scope — 'Tables that a script draws are not included' — which tells an agent when not to bother calling. It does not name an alternative tool or state conditions for choosing a different extraction sibling, so there is context but no routing guidance.

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