Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_api_html_table_parser

Parses HTML tables from a URL or raw HTML into structured JSON for downstream data extraction and analysis.

Instructions

[Web Intelligence] Parse HTML tables into JSON Measured p50 12 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://api.caelaralabs.com.

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": "caelara_api_html_table_parser"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage URL
htmlNoRaw HTML (alternative to url)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only adds latency figures (p50 12 ms, p95 15 ms) and the endpoint host. It does not say whether the url path performs a live fetch, how tables without headers or nested tables are handled, what size limits apply, or what the JSON shape looks like.

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 short and front-loads the core purpose before the benchmark and endpoint metadata. The "[Web Intelligence]" tag and the bare endpoint sentence are filler-ish but not enough to hurt readability.

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

Completeness2/5

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

There is no output schema, so the description should describe the returned JSON structure (e.g., an array of tables with rows/cells), but it stops at "into JSON". Combined with zero annotations, an agent cannot predict return shape or error behavior for a two-input parser.

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% for both parameters (url and html), so the schema already explains each one. The description adds no meaning beyond that, and notably does not clarify the mutual-exclusivity implied by "alternative to url" or that at least one is required despite required=[].

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?

"Parse HTML tables into JSON" gives a specific verb (parse) and resource (HTML tables) plus an output format, so the agent knows exactly what the tool produces. It does not, however, differentiate itself from nearby siblings such as caelara_docs_html_to_clean_text or caelara_api_url_to_markdown, which also consume HTML.

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

Usage Guidelines2/5

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

Usage is only implied by the noun "HTML tables" — there is no statement of when to prefer this over the generic HTML-to-text or URL-to-markdown siblings. No exclusions, prerequisites, or routing guidance are offered.

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