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

mcp-web-print-pdf

by weixiaoyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

printImageByBase64

Prints a Base64-encoded image to a local printer, with an optional dry-run preview and automatic data URI prefix handling.

Instructions

把 Base64 编码的图片打印。默认出纸；dry_run: true 只预览；缺 data:image/...;base64, 前缀时会自动补

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": {
      "base64": "<base64>"
    },
    "name": "printImageByBase64"
  }
}

Input Schema

NameRequiredDescriptionDefault
base64Yes图片的 base64；带不带 data:image/...;base64, 前缀都可以
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.5/5.0
Behavior3/5

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

With no annotations, the description usefully discloses the most consequential trait: by default it physically prints paper, and dry_run:true is a safe preview. However it says nothing about printer selection (printer_name, system default), that unknown pdf_options/print_options keys raise errors, or what the preview returns.

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?

Three short clauses separated by semicolons, with the core action and the default print behavior front-loaded. No filler and nothing buried.

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?

For an 8-parameter tool with nested pdf_options/print_options/extra_options, no annotations and no output schema, the description covers the action and the print/preview fork but omits printer targeting, copies, and the fact that preview returns an address. Adequate but incomplete for the tool's complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents base64, dry_run, copies and nested options thoroughly. The description adds at most a restatement of dry_run and the auto-prefix behavior, both of which the schema already states — baseline 3.

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+resource ('把 Base64 编码的图片打印'), which inherently separates it from printImageByUrl and printPdfByBase64 by naming the input format. It does not name any sibling explicitly, so a 4 rather than a 5.

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?

The default-print vs dry_run-preview split is stated, which is useful usage context. But it never says when to pick this over printImageByUrl (i.e. you already have base64 vs a URL) or when to use printFile, leaving routing to the agent.

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