Skip to main content
Glama
Sign In
EMMA MCP

EMMA MCP

by ark9164-create
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

extract_pdf_text

Extract text from official statement PDFs to pull financials, debt tables, and bond details into Excel. Focuses on downloaded PDF content for analysis.

Instructions

Extract text from a previously-downloaded OS PDF so you can pull financials, debt service tables, obligor financials, rating language, bond purpose, sources-and-uses, etc. into an Excel model. Works best on OS PDFs saved via download_official_statement.

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": {
      "path": "<path>"
    },
    "name": "extract_pdf_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the saved PDF
pagesNoPage range like '1-20' or '45,46,47' (optional — default: all)
max_charsNoCap on returned characters to protect context

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states the extraction purpose but omits safety information (read-only), limitations (e.g., OCR not supported), or output format. The cap on characters is mentioned in the schema but not in the description.

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 two sentences, front-loaded with purpose, and contains no redundant information. Every word adds value.

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 captures the core use case but lacks details on return values (no output schema) and behavioral constraints. For a simple extraction tool, it is adequate but not fully complete.

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%, so the baseline is 3. The description does not add new parameter meaning beyond the schema; it focuses on the use case rather than parameter details.

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 explicitly states 'Extract text from a previously-downloaded OS PDF' and lists specific use cases like pulling financials and debt tables, clearly differentiating it from siblings like download_official_statement and get_official_statement_pdf.

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 specifies when to use: after downloading via download_official_statement. No explicit exclusions or alternatives are given, but the sibling set does not contain other extraction tools, so the guidance is sufficient.

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