Skip to main content
Glama
Sign In
mcp-web-print-pdf

mcp-web-print-pdf

by weixiaoyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

printFile

Prints local files to a printer by auto-selecting PDF, HTML, or image handling based on file extension; supports dry-run preview before actual printing.

Instructions

打印本机文件：按扩展名自动选择 PDF / HTML / 图片通道。默认出纸；dry_run: true 只预览

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

Input Schema

NameRequiredDescriptionDefault
pathYes本机文件路径，绝对路径或相对当前工作目录
copiesNo便捷参数：份数
dry_runNofalse（默认）= 真正出纸；true = 只渲染预览。显式 extra_options.action 优先于本项
pdf_optionsNoPDF 排版选项（字段与客户端 pdfOptions 白名单一致，未知字段会报错）
paper_formatNo便捷参数：纸张名。标准纸名会同时写入 pdf_options.paperFormat 与 print_options.paperFormat；其它纸名只写后者
printer_nameNo便捷参数：打印机名，留空用系统默认打印机
extra_optionsNo额外选项：action/requestTimeout/cookies/httpHeaders/localStorages/sessionStorages，以及任意自定义键（会原样返回）
print_optionsNo打印机选项（字段与客户端 printOptions 白名单一致，未知字段会报错）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.4

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the single most important trait — that the default is real physical output (出纸) and dry_run only renders a preview — but says nothing about permission/auth needs, what happens with an unsupported extension or missing file, or what the call returns beyond the preview case.

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?

Two compact clauses: what it does, then the default/override behavior. Nothing is wasted and the side-effecting default is front-loaded.

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?

For an 8-parameter tool with heavy nesting, a detailed self-documenting schema, and no output schema, the description covers the essential orientation (auto-channel, default print, preview mode). It could have added which option block applies to which channel or that conflicting extra_options.action wins, but those are documented in the schema.

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 coverage is 100%, so baseline is 3; the description earns one more by explaining that the channel is chosen automatically from the file extension, which tells the agent what `path` actually has to point at before opening the deep pdf_options/print_options trees.

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 ("打印本机文件") plus the mechanism (extension-based channel selection among PDF/HTML/image). The phrase 本机文件 implicitly distinguishes it from the URL/base64 siblings (printPdfByUrl, printImageByBase64), but the description never names those siblings, so the differentiation is left for the agent to infer.

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?

It gives the default action and the dry_run escape hatch, which is real usage guidance for the primary decision (preview vs. actually print). However, it never says when to choose this over printHtml/printPdfByUrl/batchPrint, nor any precondition such as a configured printer or supported extension list.

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