Skip to main content
Glama

SolSignal Web Tools

PDF URL to text

pdf_to_text
Read-only

Download a PDF from a URL (up to 25 MB) and extract its text layer, page count, title and author.

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": {
      "url": "<url>"
    },
    "name": "pdf_to_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a 25 MB size ceiling, the fact that only the text layer is extracted (implying image-only PDFs yield nothing), and which metadata fields come back. It stops short of covering failure modes for invalid or non-PDF URLs.

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 sentence, front-loaded with the download action, then the extraction outcome. Every clause carries information (source, size cap, extracted fields) and there is no filler.

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

Completeness4/5

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

With only two parameters and no output schema, the description does the important work: it states the source, the size limit, and the returned fields. The remaining gap is the max_chars parameter, whose truncation semantics are left entirely unexplained despite being the only lever an agent can tune.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: url is documented in the schema as 'Public http(s) URL', but max_chars (1000–100000) has no description anywhere. The description never mentions truncation or character budgeting, so it does not compensate for the undocumented parameter an agent must reason about.

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?

The description pairs a specific verb ('Download ... and extract') with a specific resource ('a PDF from a URL') and enumerates the returned fields (text layer, page count, title, author). It implicitly separates itself from siblings like web_to_markdown and image_ocr by scoping strictly to PDFs, but it never names those alternatives, so the differentiation is inferential rather than explicit.

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?

Usage is only implied: the tool applies to public PDF URLs, and the '(up to 25 MB)' note signals a precondition. There is no statement about what to do with non-PDF URLs (web_to_markdown) or scanned/image-only PDFs that lack a text layer (image_ocr), which are the two most likely misrouting cases among the siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources