Skip to main content
Glama
Sign In
Document & FinTech Parser MCP

Document & FinTech Parser MCP

by Whambammy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pdf_table_stream_extractor_resilient

Extracts multi-page financial tables from complex PDFs, handling merged cells, ruled/unruled borders, and wrapped column baselines without misaligning cells.

Instructions

Extracts multi-page financial tables from complex PDFs with merged cells, ruled/unruled borders, and wrapped column baselines without misaligning cells. (0.040 USDC on Base L2)

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": {
      "payload": "<payload>"
    },
    "name": "pdf_table_stream_extractor_resilient"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesInput parameters or JSON string payload for the tool execution
paymentSignatureNoBase L2 USDC micropayment signature or transaction hash for x402 settlement

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does provide a behavioral promise ('without misaligning cells') and exposes the cost, but it omits input format, return shape, side effects, or limitations. Some useful behavioral context, but clear gaps remain.

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?

One front-loaded sentence defines the capability and scope, followed by a useful cost note. There is no fluff, and every element contributes to the agent's decision-making.

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?

The tool is high-complexity, but the description does not explain how to provide the PDF, what output structure to expect, or any usage constraints. With a generic payload schema and no output schema or annotations, the agent cannot reliably construct a correct invocation.

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%, but the payload parameter is described generically as 'Input parameters or JSON string payload'. The description adds no specificity about what the payload must contain or how the PDF should be passed, so it stays at the baseline 3.

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 uses a specific verb ('Extracts'), a clear resource ('multi-page financial tables from complex PDFs'), and lists distinguishing features like merged cells, ruled/unruled borders, and wrapped columns. This clearly separates it from siblings like parse_pdf_form_fields or extract_tables_from_markdown.

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?

The description implies when to use it: complex multi-page financial PDFs with merged cells and varied borders. It also mentions the 0.040 USDC cost, which is useful. However, it does not explicitly name alternatives or state when not to use this tool.

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