Skip to main content
Glama

PDF в текст

pdf_to_txt

Извлекает текст из PDF в файл .txt (UTF-8). file_url: публичный URL PDF-файла. mode: text (по умолчанию) | blocks | words. text — простой текст постранично; blocks — текст по абзацам и колонкам; words — каждое слово с координатами.

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": {
      "file_url": "<file_url>"
    },
    "name": "pdf_to_txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNotext
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, idempotentHint=false and openWorldHint=true; the description is consistent with that by stating it writes a .txt file and requires a public URL, which adds real context beyond the annotations. It omits behaviourally important facts: what happens with scanned PDFs (no embedded text layer), whether the returned file is a link or inline content, and any size/page limits for the public URL fetch.

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?

Front-loaded purpose sentence followed by two compact parameter lines and an indented enumeration of mode values. Every line carries information an agent needs; nothing is repeated from the schema or annotations.

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?

An output schema exists, so return-value explanation is not required, and the parameter semantics are well covered. For a conversion tool sitting in a family of heavily overlapping extractors, though, the missing routing guidance (OCR vs. text extraction vs. markdown/word output) leaves a meaningful gap in what an agent needs to call the right tool.

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 description coverage is 0%, so the description must carry the parameter burden and largely does: file_url is defined as a public PDF URL and each of the three mode values is given a concrete meaning ('text' paginated plain text, 'blocks' paragraphs/columns, 'words' with coordinates). It stops short of stating accepted URL schemes or that mode is the default 'text' only implicitly via the schema.

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?

States a specific verb and resource ('Извлекает текст из PDF') plus the output artifact ('.txt, UTF-8'), so the agent knows exactly what is produced. It does not, however, distinguish itself from near-neighbours such as pdf_to_markdown, pdf_to_word, or ocr_pdf, which all extract text-like content.

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 by the output format; there is no explicit statement of when to pick this over pdf_to_markdown (markdown structure), pdf_to_word (editable document), or ocr_pdf (scanned/image-only PDFs). The mode descriptions hint at use cases (layout-aware extraction via 'blocks', positional data via 'words') but never frame them as selection criteria.

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.