Skip to main content
Glama

snapforge

by org.snapforge

SnapForge PDF

snapforge_pdf
Read-only

Render a public URL or raw HTML to a PDF (returned as an embedded resource). Requires a SnapForge API key (no key? call snapforge_signup first).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPublic http/https URL to render. Provide either url or html.
htmlNoRaw HTML to render instead of a URL (max 2MB). Provide either url or html.
delayNoExtra wait in milliseconds before capture (0–10000)
marginNoCSS size applied to all margins, e.g. "1cm"
landscapeNoLandscape orientation (default false)
waitUntilNoWhen to consider the page ready: "load" (default) or "networkidle"
pageFormatNoPaper size when paginating (default A4)
singlePageNoOutput one continuous page sized to the content height (no A4 pagination)
printBackgroundNoInclude CSS background colors and images (default true)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bytesYesSize of the generated PDF in bytes
mimeTypeYesAlways application/pdf

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations provide readOnlyHint=true, openWorldHint=true, etc. The description adds context about requiring an API key and returning an embedded resource. No contradictions, but no additional behavioral details (e.g., size limits, timeouts) are disclosed.

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 sentences, front-loaded with purpose and a key usage note. No filler; every sentence adds value.

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?

The tool has 9 parameters and an output schema, but the description covers the core function and a critical prerequisite. It is sufficient for agent selection; missing details are likely in the schema and output schema.

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 coverage is 100%, so the schema already documents all parameters. The description briefly mentions 'public URL or raw HTML', a reference to two parameters, but adds no further meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Render a public URL or raw HTML to a PDF', specifying the action and resource. The title 'SnapForge PDF' and sibling context (markdown, screenshot) make the tool's purpose distinct.

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

Usage Guidelines4/5

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

The description mentions the prerequisite of an API key and directs users without a key to snapforge_signup. However, it does not explicitly compare to siblings or specify when not to use this tool.

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

All snapforge toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: markdown extraction, PDF rendering, screenshot capture, and account signup. No overlap or ambiguity.

Naming Consistency5/5

All tools follow the same 'snapforge_<format>' pattern, making them predictable and easy to distinguish.

Tool Count5/5

Four tools is well-scoped for a service that converts URLs/HTML to different formats plus a signup process. Neither sparse nor excessive.

Completeness4/5

Covers the core conversion tasks (markdown, PDF, screenshot) and the necessary signup flow. Minor missing features like configurable screenshot options, but no major gaps for the stated purpose.

Resources