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

mcp-web-print-pdf

by weixiaoyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

printImageByUrl

Downloads an image from an HTTP(S) URL and sends it to a local printer; use dry_run to preview without printing.

Instructions

下载一张图片并打印。默认出纸；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": {
      "url": "<url>"
    },
    "name": "printImageByUrl"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes图片的 http(s) 地址
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
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose the single most important trait: the default is a real physical print (出纸), while dry_run: true only renders a preview. That escape hatch warning is exactly what an agent needs before an irreversible side effect. Missing only the prerequisites (a configured printer) and 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?

Two clauses, front-loaded with the action and immediately followed by the default side effect and its override. No filler, 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?

The nested pdf_options/print_options trees are fully self-documented, so the description needn't restate them. However, with no output schema, it never says what a preview returns (a preview URL?) or that a printer must be configured — both relevant for an agent deciding whether to print or preview.

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% across all 8 parameters, including the dry_run priority note over extra_options.action, so the schema already does the heavy lifting and the baseline is 3. The description's bare mention of dry_run restates rather than extends 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 action pair (下载一张图片并打印) against a specific resource (an image at a URL), which lets an agent distinguish it from printImageByBase64 and printFile by input type. It does not explicitly name the sibling it replaces, so differentiation is implicit rather than spelled out.

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 implied: call it when you have an http(s) image URL and want it on paper. The description never names alternatives (printImageByBase64 for local data, printFile for local paths) or states when not to use this tool, 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