Skip to main content
Glama

Nordic Financial MCP

by io.github.AIDataNordic

parse_pdf_to_text

Read-only

Download a PDF from a URL and extract all text content, page by page.

Use this to read the full text of a specific document — for example, an annual report PDF linked from a search_filings result. Best combined with search_filings: use search_filings to locate the document, then parse_pdf_to_text for the full text. Do not use for PDFs that are already well-represented in the database — search_filings is faster and returns pre-ranked, relevant excerpts. Not suitable for scanned (image-only) PDFs without embedded text; those pages will be returned as "(no extractable text)".

Args: pdf_url: Direct HTTPS URL to the PDF file, e.g. https://example.com/report.pdf. Must be publicly accessible; authentication-protected URLs will fail.

Returns: All text from the PDF with "--- Page N ---" separators between pages. Returns an error string if the download fails, the URL does not point to a valid PDF, or the document exceeds the 60-second download timeout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pdf_urlYesDirect HTTPS URL to the PDF file

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.9/5.0
Behavior5/5

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

Annotations indicate readOnlyHint and openWorldHint. Description adds key behaviors: page separators, error handling for failed downloads or invalid URLs, timeouts, and behavior for scanned PDFs. No contradictions with annotations.

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?

Well-structured: opens with main purpose, then usage guidance, constraints, parameter details, and return format. Every sentence adds value, no redundancy.

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?

Given the tool's moderate complexity, single parameter, presence of annotations and output schema, the description covers all necessary context: return format, error conditions, and limitations. Fully adequate.

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?

Only one parameter (pdf_url) with schema coverage 100%. Description adds important context: must be publicly accessible, authentication-protected URLs fail, and includes an example. This goes beyond the schema's minimal description.

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 downloads a PDF from a URL and extracts text page by page. It distinguishes itself from sibling tools like search_filings, which returns excerpts, making the purpose specific and actionable.

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

Usage Guidelines5/5

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

Explicitly states when to use (full text of specific document), when not to use (already well-represented in database, scanned PDFs), and alternatives (search_filings for excerpts). Also specifies constraints like public URLs and timeout.

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

All Nordic Financial MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: analyze_company for synthesized answers, company_research for raw grouped search results, search_filings for direct database queries, get_company_info for registry data, get_current_power_price for electricity prices, parse_pdf_to_text for full document extraction, and ping for connectivity. Descriptions explicitly differentiate them, preventing confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: analyze_company, company_research, get_company_info, get_current_power_price, parse_pdf_to_text, search_filings, and ping (a single word but acceptable). No mixing of conventions or inconsistent styles.

Tool Count5/5

Seven tools is well-scoped for a Nordic financial data server. Each tool serves a necessary function without redundancy or bloat. The count covers core data retrieval, analysis, registry lookup, niche data (power prices), and utility tools (PDF parsing, health check), fitting the server's purpose.

Completeness4/5

The tool set covers the main workflows: searching filings, analyzing companies, retrieving registry data, fetching power prices, and extracting full documents. A minor gap is the lack of a direct Swedish registry lookup (get_company_info excludes Sweden, and search_filings doesn't provide registration data). Otherwise, the surface is well-rounded for Nordic financial queries.

Resources