Scholar Library

Overview Schema Source Related Servers Discussions Admin

parse_local_pdf

Extract text from a local PDF version offline without uploads. For scanned pages, run TextIn OCR; verify formulas, tables, and reading order on the original pages.

Instructions

免费离线解析PDF文字层，无上传；扫描页需TextIn OCR。公式、表格、阅读顺序须看原页复核。切换解析器会使旧引用过期。

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": {
      "version_id": "<version_id>"
    },
    "name": "parse_local_pdf"
  }
}

Input Schema

Name	Required	Description	Default
`version_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false, openWorldHint=false) and the description carries substantive behavior: free, offline, no upload, OCR required for scanned pages, and a real side effect (switching parsers expires old citations). Missing explanation of why readOnlyHint is false or what the call produces, but it adds notable context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense clauses, front-loaded with the core purpose and no wasted filler. Every clause (offline/no-upload, OCR caveat, verification caveat, citation invalidation) carries information, though the density borders on terse.

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?

Covers purpose, OCR limitation, verification caveats, and a side effect, which is solid for a simple parse tool. However, it omits any guidance on the required version_id and gives no hint of the result shape, which an agent needs given there is no output schema.

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?

The single required parameter 'version_id' has 0% schema description coverage, and the description never mentions it or explains what a version identifier is. With low coverage the description should compensate, but it adds no parameter meaning.

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?

States a specific verb+resource ('解析PDF文字层' = parse PDF text layer) with explicit scope qualifiers (offline, no upload, text-layer only). It is clearly distinguishable from the generic sibling 'parse_document' by emphasizing local/offline operation and text-layer limitations.

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?

Gives clear conditions: use for text-layer PDFs offline, but scanned pages need TextIn OCR (routing the agent elsewhere). It also warns that switching parsers invalidates old citations. It stops short of naming the exact OCR sibling tool, so the alternative is implied rather than explicit.

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