Skip to main content
Glama
rcarmo

office-document-mcp-server

by rcarmo

web_extract_tables

Read-only

Extract HTML tables from a web page and convert them into structured data with headers and rows. Optionally specify a table index to retrieve a specific table.

Instructions

Extract tables from a web page as structured data.

Fetches a page and extracts HTML tables, converting them to a structured format with headers and rows.

Example: web_extract_tables(url="https://example.com/data")

web_extract_tables(
    url="https://example.com/report",
    table_index=0  # Get only the first table
)

Args: url: The URL to extract tables from table_index: Specific table index to extract (optional, 0-based) timeout: Request timeout in seconds (default: 30)

Returns: Dictionary with extracted tables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to extract tables from
table_indexNoSpecific table index to extract (optional, 0-based)
timeoutNoRequest timeout in seconds (default: 30)
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral context: it fetches the page, extracts HTML tables, and converts to structured format with headers and rows. This goes beyond annotations, though it omits details like rate limits or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loading the purpose, then explaining the process, followed by examples and args. Every sentence is informative, with no wasted words.

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?

The description lacks an output schema, and its return note is minimal: 'Dictionary with extracted tables'. It does not specify the dictionary structure, behavior when no tables found, or error handling. For a tool with 3 parameters and no output schema, this is adequate but not comprehensive.

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 has 100% parameter description coverage. The description adds value by providing usage examples and stating the default timeout (30 seconds). This clarifies param semantics beyond the schema definitions.

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 clearly states the tool extracts tables from a web page as structured data, with a specific verb and resource. It is distinct from siblings like web_fetch (fetches raw page) and web_extract_links (extracts links).

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?

The description provides examples but does not explicitly state when to use this tool versus alternatives like web_fetch or web_extract_links. It implies usage when needing structured table data, but lacks exclusions or comparative guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rcarmo/python-office-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server