Skip to main content
Glama
Sign In
Scholar Library

Scholar Library

by SAKURAfan1023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

import_document

Import local PDF, DOCX, PNG, JPG, MD, or TXT files into your library, keeping immutable originals offline and saving each new file version separately.

Instructions

本地导入PDF/DOCX/PNG/JPG/MD/TXT，保留不可变原件；不上传。每个新文件版本单独保存。

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

Input Schema

NameRequiredDescriptionDefault
pathYes
labelNomanuscript
work_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

With annotations giving only readOnlyHint=false and destructiveHint=false, the description adds real behavioral context: the original is kept immutable, nothing is uploaded (local-only), and every new file version is stored separately. That versioning and immutability detail is valuable beyond the 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?

A tight multi-clause sentence with the verb and format list front-loaded and no filler. Every clause conveys a distinct fact, though the structure is slightly telegraphic.

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?

No output schema exists, and the behavioral profile (immutable original, local-only, per-version storage) is reasonably covered. However, with three undocumented parameters and no usage routing, the definition is not complete enough to call correctly without inspecting the 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?

Schema description coverage is 0% across all three parameters (work_id, path, label), so the description carries the full burden. It only mentions file formats, leaving work_id, path, and the label default of 'manuscript' entirely unexplained.

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 clear verb (import) and resource (document) plus the supported formats (PDF/DOCX/PNG/JPG/MD/TXT), and specifies 'local'. This distinguishes it from upload-oriented siblings, though it never names an alternative tool explicitly.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance or named alternative among the many siblings (import_references, download_fulltext, convert_document). 'Does not upload' implies a local-only context, but the agent must infer when to pick this over parse_local_pdf or import_references.

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