Skip to main content
Glama

pdf-suite

pdf_from_images

Wrap one or more JPEG/PNG images (or fall back to an annotated vector page) into a clean PDF document.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_from_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathNo
base64DataNoJPEG or PNG image bytes.
outputPathNo
imagesBase64No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and falls short: it does not say whether a file is written, whether an existing file at outputPath is overwritten, what permissions are needed, or how page size/orientation are determined. The only behavioral hint is the unexplained 'fall back to an annotated vector page' behavior.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, but the trailing parenthetical is cryptic enough to cost clarity rather than save space. Brevity here is close to under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with four all-optional parameters, no annotations, and no output schema, the description omits too much: return behavior, output destination, and input precedence are all unstated. An agent could not reliably invoke this without guessing.

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 coverage is only 25% (only base64Data is documented), and all four parameters are optional with no stated precedence among inputPath, base64Data, and imagesBase64. The description never mentions outputPath at all, leaving the agent unable to tell which inputs are mutually exclusive or required in practice.

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?

The description states a specific transformation: JPEG/PNG images wrapped into a PDF document, which is clearly distinct from siblings like pdf_from_html_text or pdf_merge. The parenthetical 'or fall back to an annotated vector page' is ambiguous and blurs the stated purpose, keeping it from 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 Guidelines2/5

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

There is no guidance on when to choose this tool over pdf_from_html_text or pdf_merge, and no prerequisites, exclusions, or input-precedence rules. Usage is only implied by the verb 'wrap'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources